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