Dataverse numeric fields character limits

[Gary_Eden]

Hi,

I have a few apps that have been running on Azure SQL for sometime but now have a request to migrate them over to using Dataverse.

I've worked through the various delegation and other PowerApp code quirks between using the different types of database and resolved these and all looked good until I tried to use the app. Submissions wouldn't save but there were no error messages to explain why.

Working through the code the fault lies with the Dataverse numeric fields.

It turns out that Whole Number fields can only be a maximum of 10 digits and Decimals and Floats are a maximum of 12 digits - I need between 14 and 20 digits (occasionally more). If you exceed the limit the row doesn't save at all.

Is there a way to increase the number of digits for these fields beyond the values noted above?

The workaround I have for the moment is to use a single line of text field and then wrap the result in Value() in order to process it... nuts.

On the topic of nuts... why on earth are auto-numbers not numbers?

Making them string-prefixed, even when you only want a number, makes the entry a string which you then have to wrap in Value() to do anything useful with it - illogical. 

Cheers

[ivan_apps]

Have you defined your dataverse whole number as a 'big' number? I believe it should solve your whole number not saving problem.

re: auto-numbers - it's called slightly incorrect, it's more like a user-friendly ID generator. Since it's created as a string type, it would never be a integer even if you store all numbers.

[Gary_Eden]

Hi @ivan_apps 

Thanks for your quick reply, it sounded promising - I hadn't spotted the Big number option.

However, the Big number fields/columns won't pull through into PowerApps - although I did notice the Version Number column was also a Big number and I can pull this through okay.

On the chance there may be a conflict with my original app and tables I spun up a new app and table to see if the Big Number fields would pull through. Still not visible although I can still display the version number. I'll stick with using text fields for now, as I'm running out of time but will come back to this in the future should the project need it.

BTW Funny that you call auto-numbers a 'user-friendly ID generator' - coming from a SQL database design background it's anything but user-friendly.

Thanks again

[ivan_apps · Accepted solution]

Yea I haven't tested the Big numbers in Canvas apps, I assume that’s what you mean by ‘pulling into powerapps’. Works on model apps though, perhaps it’s a limitation with canvas.