Does a mobile/runtime geodatabase (.geodatabase) not support all the same SQL functions as a File GDB?
I have the same data with the same label classes in a File GDB and then published to AGOL as a hosted feature service. The CHAR_LENGTH SQL function evaluates fine in each of these, but as soon as I create an offline replica (local copy/download map) from Pro, it breaks.
Hosted Feature Service:
Solved! Go to Solution.
It does appear to acknowledge LENGTH, although when I go to update the expression I still get a syntax error, so I must be missing another difference with SQLite.
Either way, I need something that will be consistent in both. So I guess I'll evaluate the label with Arcade after limiting the features with SQL. Hopefully that doesn't slow things down.
I'm open to other suggestions if anyone has any.
The syntax validators have always struggled with all the different flavors of SQL across the different DBMSs. It isn't uncommon for me to have it say something is wrong, I hit OK and save it anyways, and then it works.
At this point I don't know enough about your workflow to comment any further. As much as Arcade is an abomination that Esri should not have created, it is cross platform, which increases portability. So, even I occasionally end up having to use it, albeit grudgingly.