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