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