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