Possibility to provide relative path to a Bravo template

[Nick-C-137]

The feature request

It would be nice to be able to specify a relative path to a Bravo template. This way, it would be much easier to integrate in a git mono repository, having the template living together with the semantic model.

Right now, it seems to overwrite the path to the template with each user's full local path. This is annoying, e.g. in my team, as we are several people working on the same semantic model.

Proposed solution

Ability to specify a relative path directly in the tmdl after setup, or supporting it through the UI as well.

Additional context

No response

[albertospelta]

Hi @Nick-C-137, thanks for your feedback! We cannot change the default behavior because using a relative path would introduce a breaking change for users who rely on custom templates, especially in organizational deployments where templates are made available to users through a location accessible to all client devices (e.g., a shared folder).

But for more advanced scenarios where Git + TMDL is used, it is still possible to modify the path manually.
This can be done in TMDL by changing:

"templateUri": "file:///C:/Users/alberto/AppData/Local/Bravo/.temp/ManageDates/Templates/Config-01.template.json"
to
"templateUri": "file:///Config-01.template.json"
or
"templateUri": "tmdl:///Config-01.template.json" to explicitly indicate the use of TMDL

With this change, the relative path should be preserved and won’t be overwritten when template developers update the model by applying a new template configuration. Could you please give it a try and let us know if it works for you, or if you encounter any issues? Thanks!