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