Required JSON Data Recently, I’ve discussed how you can build flexibility into your flows if the JSON data returned by an API contains a null or an empty string. Today I’ll look at how you can validate that the API […]
Specifying Required JSON Data Read More »
Empty JSON Strings When APIs have no data, generally either a null value or an empty string is returned. Last week in my post Handling Incomplete JSON Data, I discussed how to handle null values. Today I’ll explain how to
Handling Empty JSON Strings Read More »
Incomplete JSON Data Another day on my JSON journey. Today I’ll explain how you can build flexibility into your flows by improving the format of a JSON schema to handle incomplete data, in particular when an API returns a null
Handling Incomplete JSON Data Read More »
This is a very useful tip that makes working with JSON content in Power Automate much easier! I’ve discussed in previous posts how to understand and navigate a JSON structure, so if you need guidance with this, then check out
Simplify JSON Content Before Parsing! Read More »
Upgrades and Updates When importing a managed solution, a decision is required to either upgrade or update the existing solution. Upgrades are intended for deploying significant changes, like new features, structural changes, or adding new tables. The ‘Stage for Upgrade’
Importing a Managed Solution. Upgrade or Update? Read More »
Power Platform solutions are version numbered using the format: <Major>.<Minor>.<Build>.<Revision> For example, when a solution is created in a development environment, it will initially have the version 1.0.0.0. Revision Number The first time the solution is exported, the Revision is
Solution Version Numbering Read More »
