Fortimize Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.

1. Which org are we in?
2. Try F12 and check the console.
3. You know this will be an easy fix!
4. Let’s roll back to the previous version.
5. It’s a simple declarative change!
6. Check the field history tracking.
7. Do you have admin access?
8. You want how many validation rules?
9. Sure, we can add another picklist.
10. Lightning is still a bit... quirky.
11. That’s definitely a UX issue.
12. Have you looked at the data model?
13. It’s probably a permissions issue.
14. Have you heard about the new API?
15. Looks like another Apex batch job.
16. That’s out of scope.
17. Could be a DML error.
18. So, what’s the business process here?
19. It’s just a Visualforce page.
20. It’s a feature, not a bug.
21. There’s a Trailhead for that.
22. Oh, that’s a Salesforce limitation.
23. I have an app for that!
24. Which browser are you using?
25. Where is that object stored?
26. Did you deploy that change set?
27. When did this last work?
28. Let’s just create a quick formula for that.
29. Where did the data go?
30. That’s a custom app feature.
31. Did you look at the schema builder?
32. Just create a new record type.
33. Any integrations involved?
34. Sure, I’ll write a trigger.
35. Not supported in Lightning yet.
36. The sandbox is out of sync.
37. Is that an AppExchange product?
38. Need to customize standard objects?
39. That’s a nice use case!
40. How many profiles do you have again?
41. Let’s clone the process.
42. How many sandboxes do we need?
43. This is going to need more documentation.
44. Did you refresh your tab?
45. Check out the AppExchange.
46. Could be a governor limit.
47. We’ll need to add an object for that.
48. Another custom field?!
49. That’s a managed package issue.
50. Have you cleared your cache?
51. Can we just use a formula field?
52. I’ll take a look in Setup.
53. Did you update the security settings?
54. How did it work before?
55. I’ll just assign it to myself.
56. Let me clone this user story.
57. When’s the next release?
58. That’s just an undocumented feature!
59. You didn’t change the API name, right?
60. Looks like a JavaScript error.
61. Can you record your screen?
62. Just a quick update in Production.
63. Are you on the latest API version?
64. Did you try it in incognito mode?
65. I’ll look at the debug logs.
66. We’re running out of licenses.
67. Let’s deprecate that!
68. Let’s escalate to Salesforce Support.
69. It’s in the sandbox.
70. Classic or Lightning?
71. One more field won’t hurt.
72. We might need a flow for that.
73. Did you configure it correctly?
74. There’s a code snippet for that!
75. Have you tried turning it off and on again?
76. Yes, we can do that in Lightning.
77. Try clearing your browser history.
78. Probably need a roll-up summary.
79. Can you do it without code?
80. Let me check Stack Exchange.
81. Let's just hardcode it.
82. Salesforce was down for 5 minutes.
83. Did you check the release notes?
84. That’s an unmanaged package!
85. You might need a second admin.
86. There's a setting for that somewhere.
87. Another picklist, another problem.
88. Is it standard functionality?
89. Just add a validation rule.
90. Have you tried Classic?
91. Just install the app in your sandbox.
92. Did you check the logs?
93. Let's create a process builder!
94. Can you make a sandbox refresh request?
95. Can we avoid using code?
96. Let’s jump on a quick call.
97. Let’s put it in a Flow!
98. You need a full copy sandbox.
99. Add that to the backlog.
100. Just one more sandbox refresh.