ChrisF323949498
Tera Explorer

 

Your record wasn't saved.

Your ACL has 'admin override' ticked and you are admin, so your new ACL isn't working just for you

You're still impersonating your test user, and wondering why you can't edit a system file (business rule, etc)

You are in the wrong Scope.

You are in the wrong update set.

You are in Production! doing dev by accident.

You've forgotten to give the user a group or a role.

You didn't save the users password, when you updated it.

You didn't have a cup of coffee this morning.

You had too many cups of coffee this morning.

The time zone of your instance is skewed, so your timestamps are confusing you.

You've dot walked, to the wrong field on the wrong table.

Your Database view has the wrong order value or invalid WHERE clause.

You're not using the correct prefix on your database view field.

You've forgotten to share the report with users or roles/groups.

You've forgotten to share your dashboard.

Your target users don't have the roles to see the data you want them to see.

You didn't have a cup of coffee this morning.

You didn't have a second cup of coffee this morning.

You've spent too many hours looking at this issue, go for a 5 minute walk and come back.

You didn't close out your "", or your mixed '' with "

You've used = not ==

You forgot the

you forgot the ;

You forgot the "javascript:" prefix on your reference qualifier

You're using the label, not the field name

You forgot to add .query() to run the wonderful query you've just written.

Your dev data is old, bad, or generally incongruent/unrealistic.

Your script didn't have .update() so did nothing.

You're trying to access a value that wasn't there (Reference errors, etc).

You forgot a break clause on your loop, it's still looping…and looping…

You're off by 1.

You didn't test the 'unhappy' path

You tested everything, in depth, as admin… oops.

You're still off by 1.

 

Happy Friday!

Please add more in the comments - Jokes aside, if you're aware of them, you can often avoid them.

2 Comments