(Urgent) When and where to use Patch a Solution in PowerApps

(0) Share

Report

Posted on by JatinSaini

428

Hi Developers,

I am currently working on a PowerApps solution that includes a canvas app. My goal is to keep the solution within a single environment and not migrate it to any other environments. However, I need to design the app in a way that allows me, as a developer, to continue adding new features while ensuring that only selected features are made available to users in the future.

Additionally, I want to continue working on other areas of the app and publish updates whenever necessary, but without releasing the features I’m not ready to share yet.

Would using a patch be a viable solution for this use case? If not, I would appreciate any suggestions for the best approach to meet these requirements. Please feel free to ask for any additional details if needed to better understand my scenario.

Thanks in advance for your help!

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (0)

WarrenBelz 153,075 Most Valuable Professional on at

Like (0)

Report

Hi @JatinSaini

Patch refers to updating data, not source code.

Power Apps is not "modular", so you cannot release part of the current version of the app without the rest.

Very messy to control and risky to manage but you could have staged versions using "save as" and release them as needed (you would need another environment to publish them to and then rename), but it is not something I would recommend.

Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.
MVP (Business Applications) Visit my blog Practical Power Apps Buy me a coffee

Was this reply helpful? Yes No
JatinSaini 428 on at

Like (0)

Report

Thanks for your helpful response @WarrenBelz

So what could be the ultimate conclusion for this requirement as per your experience? Does this functionality ever come useful or can we not have the versioning management just like we have in Git for PowerApps?

Was this reply helpful? Yes No
WarrenBelz 153,075 Most Valuable Professional on at

Like (0)

Report

Not sure on your question - if you are referring to the second option, I have never tried it. The versioning management is currently as I described and I do not know of any plans to change it.

Was this reply helpful? Yes No
Suggested answer

Garima_PowerPlatform 170 on at

Like (0)

Report

Hi Jatin,
Use Feature Flags:

Implement a feature flag mechanism. This allows you to dynamically enable or disable specific features within a single app instance without publishing separate versions.

If(
LookUp(FeatureFlags, FeatureName = "NewFeatureA").IsEnabled,
DisplayNewFeatureA(),
DisplayOldFeature()
)

Was this reply helpful? Yes No