Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Gday,
At our site, saving a report in Jan 2019 PBIRS (on prem) will make it unusable in August 2018 PBIRS. Is this a known issue? If so how are people managing a 2019 dev environment while still running a 2018 live environment? Id like to have a number of users testing the 2019 release before deployment but this seems like a massive problem now because reports are not movable between the two environments. Any tips?
Cheers
Yes. Any work you do should use Aug 2018 PBI desktop. For the most part you want to test for any regressions for things that should transfer over from the Aug 2018 Prod environment. The new feature additions to PBI desktop (from aug to jan 2019), will need to be tested on the Test environment (Jan 2019).
The work done by the PBI RS team lags the service by a few months. Most of the work is implementing the features from PBI desktop server side. So it makes sense to test your existing PBI reports (Aug 2018) to ensure that they will still work once you upgrade to Jan 2019.
Cheers,
Thanks for your reply. My question was more centered around how people are managing having two clients installed on a users/testers machine. I can install 2 clients by using 32/64bit editions but then the latter client (Jan 2019) will become the default.
Im just after best practices for tesing 50 ish reports when the testers are also responsible for production reports.
Cheers
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |