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