Re: PowerApps does not recognise columns with Big ...

halghasra · ‎01-09-2023

Hi there,

I'm building a canvas-app, and I connected my app to a Dataverse table that contains some columns with big whole number data types.

However, powerApps does not recognise any of the big whole number columns, all other columns are visible and can be used -for example in LookUp functions-, but my big whole number columns do not.

To add more context, I am trying to change the default property of a Text input to display the value from the selected Dataverse row. Is this a common issue? is there a solution to this problem?

Thanks in advance!

iAm_ManCat · ‎03-15-2023

Hey @halghasra

Have you published your changes to the Table?

I was able to do a lookup to Whole number row with the maximum possible Whole Number value set:

Cheers,

Sancho

@iAm_ManCat

My blog

Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!

Thanks!
You and everyone else in the community make it the awesome and welcoming place it is, keep your questions coming and make sure to 'like' anything that makes you 'Appy
Sancho Harker, MVP

halghasra · ‎03-15-2023

Hi Sancho,

Thanks for the reply. I have no issues with whole numbers, my issue is with "Big" Whole numbers which doesn't get recognised by PowerApps.

iAm_ManCat · ‎03-15-2023

Mmm, Yes I see - I experience the same although I think this is something that would be limited by the way canvas Apps handles numbers - I don't think BigInt type is supported natively yet - you have to use API/flow to get those values.

Here's some details from an older release wave where they say they have allowed BigInt to be used, but only via API (canvas and other access to come in future):

Availability of BigInt as an API only data type - Power Platform Release Plan | Microsoft Learn

@iAm_ManCat

My blog

Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!

Thanks!
You and everyone else in the community make it the awesome and welcoming place it is, keep your questions coming and make sure to 'like' anything that makes you 'Appy
Sancho Harker, MVP

Boneckrh19 · ‎06-24-2023

I'm finding it hard to believe that there is nothing informing the user when they make a number field big that this will severely limit its use! I would have made it a text field if I had known. That this field cannot be used in apps makes it completely useless for me.

halghasra · ‎06-26-2023

I know it is frustrating! Using a text field would not help if you want to perform some calculations on these figures. My workaround solution was to use some exponentiation notations, i.e., change the type to decimal, then increase the number of decimal places to the maximum (10 digits), so whenever I patch the number to DV, I divide multiply it to 10^-5 to preserve the full number in an exponent of 5, and whenever I need to display it within the app, I multiply it by 10^5.