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