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