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