sql-bi / Bravo

Bravo for Power BI
MIT License
352 stars 92 forks source link

Unable to update a date table defined by another user's template #764

Closed preston-reynolds closed 9 months ago

preston-reynolds commented 9 months ago

Describe the problem

Here's the scenario I'm running into:

Error HTTP/500: Internal Server Error. Could not find a part of the path 'C:\Users\<USERNAME>\<COMPANY NAME>\Business Intelligence Agency - Documents\Internal Reports\Date Table Templates\BIA\dist\BIA.package.json'. Trace Id: 00-81e73c083dd9d083986cd6c080567cb2-8bc06fc0cab15a88-00 Version: 1.0.6 (1.0.8693.18732)

The issue here is that once a custom template is used, unless the template resides in the exact same location for the user, (this really becomes a problem when the user is different from the original user), you are unable to update/select a date table definition template.

Bravo version

1.0.6 (1.0.8693.18732)

Tabular model

Power BI Desktop, import mode

Power BI

2.124.1805.0 64-bit (December 2023)

Steps to reproduce the behavior

No response

Additional context

No response

Screenshots

No response

Anything else ?

Trace Id: 00-81e73c083dd9d083986cd6c080567cb2-8bc06fc0cab15a88-00

albertospelta commented 9 months ago

@preston-reynolds We have a fix for this issue that will be available in the next version, set to be released in a few days. If you'd like to test it, you can get the latest internal build by changing the update channel from stable to dev in the Options\About panel and following the link to download the installer.

This update allows the override of the template path applied by the original user by specifying an alternative path to use. After installing the version containing this fix, it should be enough to add your custom template to the list of templates within the Options\Templates panel. Then, through the Browse... button, you can then specify the effective path to use.

We will release the new version next week. In the meantime, if you could try out the internal/dev build and let us know if it resolves the issue, it would be greatly appreciated.

albertospelta commented 9 months ago

Fixed in version 1.0.7