Data Types for Decimals/Currency Appsheet > Bigquery

I am a little stumped trying to use BigQuery as a data source.

One table has a field for price/currency. The table in BigQuery has a data type of FLOAT, initially I had Appsheet set to Price but I get a error that reads:

Cannot create parameter HEADER_TOTALr0 of type Float64 with value 4.35 of type System.Decimal

I tried to test other data type configs on both sides but regardless of what I have set for datatype on Appsheet or BigQuery.

Has anyone come across this?

I’ve been using a small CloudSQL instance with the same app for quite some time without issue.

Please contact AppSheet Support for help with this.

https://www.appsheet.com/Support/Contact

1 Like

Hi Steve,

Thanks for all the great replies.

I’m busy setting up my BigQuery db, is there a guide for which data types in BigQuery works best for which data types in AppSheet? Or should I just make all String as in a spreadsheet?

Thanks

above @Steve

I’ve never used BigQuery, nor am I familiar with the available documentation for its use an AppSheet.

So… Has there been any update to the support for BQ FLOAT columns?

There are still errors being produced for the simplest cases, which is AppSheet Decimal type mapping to BigQuery Float columns.

Unable to update row in table ‘table3’. → Failed to update rows (big_query): Unable to use value of type System.Decimal in BigQueryParameter

I am unaware of any changes. Please contact AppSheet Support for help with this.

Attn @Aleksi @Rob_Just

This is a HUGE BUG. There is no way to enter data into BQ tables that contain FLOAT columns, or NUMERIC columns. This includes the AppSheet data types DECIMAL, PERCENT, and PRICE. The data types cannot be saved to BQ tables.

Yeah I had the same issue still. I was testing it for a small personal project so I just left everything in cloud SQL but BigQuery doesn’t seem like a fully viable data source right now.

There’s ANOTHER MAJOR BUG as well. Null values cannot be entered period. All data types are affected. Not possible! Incredible!

These BUGS are very easy to reproduce.

Go to BigQuery in Google Cloud Console

  • Create a new table
  • Add a new column, FLOAT

Go to AppSheet

  • Create a new application
  • Choose the BigQuery data source
  • Choose the table created above
  • Wait for the new application to be created
  • Now try to enter some data into the table

You should see an error that says “Unable to use value of type System.Decimal in BigQueryParameter”

FYI, AppSheet Support has been contacted. But of course, this may awhile for any kind of resolution.

If anyone is hitting these bugs then please add a comment or two here. A larger crowd always gets more notice.

For a MAJOR BUG like this, you’d think that someone from the AppSheet team would be piping, and asking for more details. :weary_face:

@jstreit Can you add “[BUG]” to the title? Maybe that will get some attention.

This may help to make some decisions.

Received this from AppSheet support…

Hello …,

Thanks for your patience on this.

I’ll need to consult the AppSheet engineering team regarding your issue.

We’re attempting to reproduce this locally, so please allow us some time to review your request and investigate your issue.

AppSheet engineering may contact you directly through this channel If they need additional information.

1 Like

Still waiting for a reply from AppSheet support / engineering… If only there was someway to post a bug to AppSheet. :frowning:

Hello JAG,

We reached out earlier today via ticket to clarify some questions. Just wanted to give you a heads up in case you haven’t seen the message.

Also, thanks for notifying us of this issue via support. We do take bugs like this seriously. I apologize for the delay but we are working on reproducing the issue and working with our engineering team.

Thanks!

1 Like

Hey all,

We have been talking with some of the other engineers internally and were able to come up with a fix. Here we have just verified that we are able to add rows from Appsheet (Price and Decimal) to BQ type FLOAT. We are in the process of rolling this fix out to all users. The issue should be resolved once the release goes through today. Let us know if you have any other questions or concerns here.

Best,

Julian

1 Like

I sure hope the release contains fixes for both BUGS.