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