cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Frequent Visitor

Different Decimal Interpretation in identical Flows

Hey

 

I have already postet a similar topic but I could manage to break down my problem to it's bare minimum.

The result absolutely dazzles me.

 

I have a Flow (Manual Trigger, Sets the field of a Dynamics Record to "1.5")

flow1.PNG

As you see there is a record identifier and a value (hard coded). It works fine and the field of that record will be ser to 1.5

 

I have an (almost) identical Flow using Powerapps. The only thing that comes from powerapps is the record identifier:

flow2.PNG

Again, I hard coded the field "Days of Absence" to be set to 1.5. 

However, this flow sets the fieldvalue to 15 and not 1.5

I tried different numbers (1.25 => 125; 2.3 => 23 etc.)

 

Why in the world would those two flows not share the same outcome?
Does the Flow copy the regional Settings of Powerapps?

 

PS: While testing I found out that if I resubmit the Flow using Powerapps as Trigger (Test > Using data from previous run), it will work fine and set the field value to 1.5. It only doesn't work when submitting data from Powerapps.

I am heavily confused!!!!

 

Can anyone give me some advice here?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

hi @v-monli-msft

 

I found a solution or better, a workaround.

Casting my number as string (string("powerapps variable")) will submit the number correctly format.

Why I don't know, but as long as it works, I'm ok with that.

 

Regards

Mangescom

View solution in original post

3 REPLIES 3
Highlighted
Community Support
Community Support

Hi @Jonas_Portmann,

 

Your issue is quite odd, it should have the same result whether using resubmitting or trigger from PowerApps. Would you please try to fill the other fields in the Update a record action to see if it behaves the same with the Days of Absence field?

 

Regards,

Mona

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted

Hi @v-monli-msft

 

Thanks for your reply!

 

This behaviour only exists with decimal fields. I do have another decimal Field, wich will react the same.

However, it works fine for strings and wholenumbers (not too much that can go wrong here), as well as date formats.

 

On the manually triggered Flow I can "recrate" my problem by changing the local settings to a "wrong" country (dot VS comma as decimal seperator). However, the flow using powerapps as trigger has the same local setting as my powerapp and my CRM system (EN-UK).

Highlighted

hi @v-monli-msft

 

I found a solution or better, a workaround.

Casting my number as string (string("powerapps variable")) will submit the number correctly format.

Why I don't know, but as long as it works, I'm ok with that.

 

Regards

Mangescom

View solution in original post

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Top Solution Authors
Top Kudoed Authors
Users online (9,014)