In Git, each Fabric item folder using format version 2 carries this system file, which stores the item's type, name, description and logicalId. Don't alter the logicalId, as it is what matches the item across workspaces and branches; older version 1 folders held this information in item.metadata.json and item.config.json.
Also called .platform.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Platform file in context, with comparison tables and the common traps.
Terms in this definition
- Git
A distributed version control system. Anything kept in Git, prompts included, gains a history of authors, timestamps, diffs and tags, and changes can be reverted.
- FORMAT
A DAX function that turns a value into text according to a format string, for instance "MMMM" to show a month's name. Since the output is text, numeric operations can't use it, and dynamic format strings were introduced to get around that.
- Chat message roles
Labels on chat messages: instructions go under system, the person's input under user, the model's previous answers under assistant, and results returned by a called tool under tool (or function).
- logicalId
An ID that Fabric generates and stores in each item's .platform file so Git can keep matching the item to its folder after a rename, and across workspaces. Leave it unchanged.
Related terms
- Item definition
The set of files that describes a Fabric item when it is stored in Git or sent through the REST API, including a .platform file carrying its type, display name and logicalId. It contains the item's code and metadata but none of its data.