Why it's important to keep your fields in-order

[Callum.Boase]

When building your app, it’s (surprisingly) important to keep your database fields in-order.

“In order” means that fields are listed BELOW any dependencies they have (ie if they reference other fields via conditional rules, validation rules, equations or text formulas).

The reason? If fields are NOT in oder, it can lead to field values calculating incorrectly (eg a conditional rule not setting the correct value).

See this video for a full explanation and a worked example.

Why to keep your Knack database fields in-order!

I’ve seen this problem in quite a few different apps (clients come to me with this issue, totally confused about why their logic isn’t working as they expect!). Have you encountered this issue?

[CarlHolmes]

The order of operation is important and can easily be overlooked. Like you, I have seen many situations in client apps where the fields are in the wrong order so do not calculate until a second edit is completed.

About Equations

[Callum.Boase]

I actually only recently found that in the documentation!
Definitely a tricky one!