Add Sharing macros, BPA rules, and preferences article#361
Open
justBlindbaek wants to merge 4 commits into
Open
Add Sharing macros, BPA rules, and preferences article#361justBlindbaek wants to merge 4 commits into
justBlindbaek wants to merge 4 commits into
Conversation
The page's own applies_to metadata already lists all three Tabular Editor 3 editions as fully supported, but the description field still called it an Enterprise Edition feature. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Covers keeping MacroActions.json, BPARules.json, and Preferences.json in sync across a team: where shared config should live relative to a semantic model's own repository, BPA's native rule-collection support, and three options (symlink, pre-commit hook, dotfiles-manager tool) for the fixed local path Tabular Editor reads macros and preferences from, since that has no native multi-source equivalent. Adds it to the Parallel development section of the site nav, with reciprocal links to and from the existing parallel-development article. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-361.westeurope.azurestaticapps.net |
1 similar comment
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-361.westeurope.azurestaticapps.net |
mlonsk
reviewed
Jul 14, 2026
|
|
||
| # Sharing macros, BPA rules, and preferences across a team | ||
|
|
||
| Tabular Editor reads several configuration files from a fixed location on each user's machine — `%LOCALAPPDATA%\TabularEditor3\` for Tabular Editor 3, or `%LOCALAPPDATA%\TabularEditor\` for Tabular Editor 2 — most notably `MacroActions.json` (the user's macros), `BPARules.json` (the user's local BPA rules), and `Preferences.json` (general application preferences). That's a sensible default for a single developer, but teams that want a shared, consistent set of macros or preferences — across everyone on the team, across a department, or between local development and CI — run into an obvious question: **how do you keep a file at a fixed local path in sync with something version-controlled and shared?** |
Collaborator
There was a problem hiding this comment.
Add reference for more information to https://docs.tabulareditor.com/en/references/supported-files.html
| Tabular Editor reads several configuration files from a fixed location on each user's machine — `%LOCALAPPDATA%\TabularEditor3\` for Tabular Editor 3, or `%LOCALAPPDATA%\TabularEditor\` for Tabular Editor 2 — most notably `MacroActions.json` (the user's macros), `BPARules.json` (the user's local BPA rules), and `Preferences.json` (general application preferences). That's a sensible default for a single developer, but teams that want a shared, consistent set of macros or preferences — across everyone on the team, across a department, or between local development and CI — run into an obvious question: **how do you keep a file at a fixed local path in sync with something version-controlled and shared?** | ||
|
|
||
| **If what you're trying to share is BPA rules, this is already solved** — see [Sharing BPA rules](#sharing-bpa-rules) below. The rest of this page is mainly about macros and preferences, which don't have the same native support. | ||
|
|
Collaborator
There was a problem hiding this comment.
Add a high-level description of the method in proprosed and a small infographic if possible to give the user a better understanding what is being proprosed.
|
|
||
| Whichever you choose, the sync mechanisms described later on this page work the same way regardless — a dedicated macros repository just means they need to reach into a second repository rather than one you already have checked out. | ||
|
|
||
| ## Sharing BPA rules |
Collaborator
There was a problem hiding this comment.
imo, since sharing BPA rules is already solved, as noted earlier, this section should be last in this article as an addendum rather than appearing before the actual solution of the problem.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://delightful-mud-081affe03-361.westeurope.azurestaticapps.net |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces sharing-macros-bpa-rules.md, covering how to keep MacroActions.json, BPARules.json, and Preferences.json in sync across a team: where shared macros and rules should live relative to a semantic model's own repository, BPA's native rule-collection support for sharing rules with no extra tooling, and three options (symlink, pre-commit hook, dotfiles-manager tool) for the fixed local path Tabular Editor reads macros and preferences from, since that has no native multi-source equivalent. Adds it to the Parallel development section of the site nav, with reciprocal links to and from the existing parallel-development article. Also fixes a stale Enterprise-only claim in the Built-in BPA Rules page's description metadata, which contradicted its own applies_to block.