cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
CharlesS
Advocate III
Advocate III

Dataflow error: Error code: 0x80040265, Message: String was not recognized as a valid Boolean.

Hello!

I have a complex dataflow that has been running smoothly for over a month... until this morning. It is a Standard V1 dataflow.

 

Starting today, I have begun getting failed upserts, with the following error message:

Error code: 0x80040265, Message: String was not recognized as a valid Boolean.

 

I am importing data into Yes/No columns (fields). This is an example of what I am loading: 

"cra0c_shipcomplete":"false"

 

Anyone else suddenly getting this issue?

1 ACCEPTED SOLUTION

Accepted Solutions
CharlesS
Advocate III
Advocate III

After much troubleshooting, I was able to find the cause of the error and solve the problem. It turns out that this message had nothing to do with importing yes/no fields, but was rather related to a problematic business rule.

 

If ever you have a similar problem, here are the steps to solve it:

1. Start by checking your business rules for the relevant entity.

2. Pay particular attention to any conditions including numeric comparisons for fields that are imported using the dataflow, such as FieldA is greater than X.

3. If, when importing this field, it sometimes includes null values, you will receive this error in your dataflow log and the record upload will fail.

4. To solve this problem, add a new condition before your numerical comparison condition in your business rule. The new condition should be as follows : IF FieldA Does not Contain Data. 

5. Place your previous numerical comparison condition under the FALSE branch of the newly created IF FieldA Does not Contain Data condition.

6. Refresh your dataflow again.

7. Rejoice.

 

Basically, the "String was not recognized as a valid Boolean" error refers to the fact that the business rule was unable to get a valid TRUE/FALSE value from the numerical comparison of a null value.  Indeed, IF null < 3 = error.

 

Hope this explanation can help others!

View solution in original post

4 REPLIES 4
CharlesS
Advocate III
Advocate III

@KSven : I'm thinking you have some experience with dataflows... have you had issues lately importing Yes/No (Boolean) values into Dataverse?

Hi @CharlesS ,

 

actually I'm working with Dataverse / Dataflows like a Data Warehouse incl. some ETL / ELTL processes, so yeah I guess I got some experience, but unfortunately I haven't used True or False with standard v2. Just choice columns with the regarding number.

But anyway one of the following columns should work as a dataflow column, cause these are the results out of dataverse connector in Power Bi (or ODatafeed connector as well):

 

Yes/No :

I guess you have already tested datatype String/boolean? You could also try simple Yes / No as string...

KSven_0-1613027623190.png

 

Choice:

Acutally works fine for me with the ID (e.g. 0 or 4)

KSven_0-1613028061729.png

 

 

 

Hope it helps little bit. Regarding to dataflows Ive already 2 open support tickets..

 

BR,

Sven

CharlesS
Advocate III
Advocate III

After much troubleshooting, I was able to find the cause of the error and solve the problem. It turns out that this message had nothing to do with importing yes/no fields, but was rather related to a problematic business rule.

 

If ever you have a similar problem, here are the steps to solve it:

1. Start by checking your business rules for the relevant entity.

2. Pay particular attention to any conditions including numeric comparisons for fields that are imported using the dataflow, such as FieldA is greater than X.

3. If, when importing this field, it sometimes includes null values, you will receive this error in your dataflow log and the record upload will fail.

4. To solve this problem, add a new condition before your numerical comparison condition in your business rule. The new condition should be as follows : IF FieldA Does not Contain Data. 

5. Place your previous numerical comparison condition under the FALSE branch of the newly created IF FieldA Does not Contain Data condition.

6. Refresh your dataflow again.

7. Rejoice.

 

Basically, the "String was not recognized as a valid Boolean" error refers to the fact that the business rule was unable to get a valid TRUE/FALSE value from the numerical comparison of a null value.  Indeed, IF null < 3 = error.

 

Hope this explanation can help others!

View solution in original post

EricRegnier
Super User II
Super User II

Cheers for the update @CharlesS. I've experience similar issues with Dataflows as backend updates occur, what I've done unfortunately is simply re-create them...

 

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

Power Apps Community Call

Monthly Power Apps Community Call

Did you miss the call?? Check out the Power Apps Community Call here!

secondImage

Experience what’s next for Power Apps

See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (28,580)