Applies to Product - Power Apps
What’s happening?
Users are experiencing multiple pop-up errors when integrating data from Power BI into PowerApps. The errors occur for blank data fields, particularly for numeric and date types, which do not break functionality but appear untidy and incorrect to users.
What’s happening?
Users are experiencing multiple pop-up errors when integrating data from Power BI into PowerApps. The errors occur for blank data fields, particularly for numeric and date types, which do not break functionality but appear untidy and incorrect to users.
Reason:
The pop-up errors are triggered by blank values in numeric and date fields during the integration process from Power BI to PowerApps. Specifically, the errors include messages indicating that expected values are not in a valid format, such as RFC 3339 'full-date' or 'date-time' format.
The pop-up errors are triggered by blank values in numeric and date fields during the integration process from Power BI to PowerApps. Specifically, the errors include messages indicating that expected values are not in a valid format, such as RFC 3339 'full-date' or 'date-time' format.
Resolution:
To suppress the error pop-ups, the following formula can be applied to the Text property of the label in PowerApps: - Use the formula: If(IsBlankOrError(attribute), "", attribute)
Additionally, the following steps were taken to address the issue: 1. A new integration was created with just a few fields of different types to test the behavior. 2. The handling code was added one screen at a time to reduce the occurrence of pop-ups. 3. It was confirmed that the issue persists despite attempts to handle blank values, indicating that further adjustments may be necessary on each screen where data integration is utilized.
If the issue continues, further investigation into the specific configurations and settings within PowerApps may be required.
To suppress the error pop-ups, the following formula can be applied to the Text property of the label in PowerApps: - Use the formula: If(IsBlankOrError(attribute), "", attribute)
Additionally, the following steps were taken to address the issue: 1. A new integration was created with just a few fields of different types to test the behavior. 2. The handling code was added one screen at a time to reduce the occurrence of pop-ups. 3. It was confirmed that the issue persists despite attempts to handle blank values, indicating that further adjustments may be necessary on each screen where data integration is utilized.
If the issue continues, further investigation into the specific configurations and settings within PowerApps may be required.