![]() ![]() Note that this is an experimental feature. ![]() But this will get you started and will continue to be supported with those enhancements. We have plans to further simplify this with better untyped object array support and casting as a whole via a schema rather than field by field. This is both easier to read and more robust, tolerating reordered and additional fields. ProductName: Text( Value.ProductName ) } ) With the new ParseJSON function, this can be written as: ForAll( Table( ParseJSON( ProductRecommendationsJSON ) ), However, it is hard to write and verify with that complex regular expression syntax and is fragile, for example it will break if the order of the JSON fields is changed or another field inserted.Ī better answer is a dedicated JSON parser, a highly requested feature on our community ideas forum. This works and is what the customer shipped their app with. So, like many of you, we turned to regular expression matching using this formula: MatchAll( ProductRecommendationsJSON, However, the volume and latency of these calls didn’t work for their scenario. Their first solution was to use a Microsoft Power Automate flow to do the parsing which has excellent JSON support. For example, we recently worked with a customer who needed to extract information from a relatively simple JSON string stored in a Dataverse table: [ This new function dramatically simplifies working with JSON in Canvas apps. We are pleased to announce the experimental release of our ParseJSON function, which can parse JSON strings into Power Fx objects and types. ![]()
0 Comments
Leave a Reply. |