userdata
1 TopicMSIX AppAttach FSLogix Profile issue between packaged app versions
Has anyone experienced the following scenario: Application (PowerBI) packaged as MSIX and delivered via App Attach: Package Name: PowerBI-2.104.702.0.MSIX Delivered via App Attach to AVD FSLogix Profile created, and Application user data stored path: \\CLIENTNAME.file.core.windows.net\fslogix\$GUID_username%\Profile_User_name.vhdx\ Profile\AppData\Local\Packages\PowerBI-2.104.702.0\LocalCache\Local\Microsoft\Power BI Desktop (or similar) End user can access application, app profile data is retained to FSLogix and works as expected between sessions, retaining app settings etc. Now, a new version is required: Package Name: PowerBI-2.104.941.0.MSIX Delivered via App Attach to AVD FSLogix Profile created, and Application user data stored path: \\CLIENTNAME.file.core.windows.net\fslogix\$GUID_username%\Profile_User_name.vhdx\ Profile\AppData\Local\Packages\PowerBI-2.104.941.0\LocalCache\Local\Microsoft\Power BI Desktop (or similar) So, between the different versions of the same Application, I am not able to access the roaming profile application data from the original package, forcing my users to have to re-configure the application afresh for the new release. I could just repackage the new version using the EXACT SAME name, but this makes it impossible to differentiate between packages, and also does not meet any version control naming conventions. Has anyone come across this before, and has anyone discovered a viable solution? Thanks NickSolved2.2KViews0likes2Comments