Forum Discussion

dbeavon3's avatar
dbeavon3
Memorable Member
4 years ago

Prevent saving linquistic metadata

Unfortunately Microsoft has given us very little support for tracking PBI changes with source control.

 

However I'm trying to muddle forward with this anyway ... since change tracking is a fairly important concern (whether or not Microsoft may agree).

 

I've been connecting to my XMLA endpoint on premium and extracting the model from SSMS.  This is a step I do after every change so I am able to see/review diffs between versions.  However I'm fighting my model over a massive amount of garbage that is currently residing under the JSON elements at /model/cultures/linguisticMetadata.

 

This "linguistic metadata" code is growing to almost 70% of the bim, after export.  That is totally unreasonable and I don't want to wade thru these noisy diffs whenever I'm in the process of adding a new version of the model to source control.  

 

Which brings me to the question.... how to I prevent the storage of this "linguistic metadata" that we don't want or need?  This needs to be removed from the model if possible.

 

 

Need Help

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    Hi dbeavon3,

    Unfortablely, we are not able to do customs with these metadata generations. Perhaps you can try to submit an idea to improve these traced response metadata.

    Microsoft Power BI ideas
    Regards,

    Xiaoxin Sheng

  • fuxia84's avatar
    fuxia84
    Frequent Visitor
    6 months ago

    I totally agree I started to work with TMDL in Visual studio code and every time I m doing even a small change on the report I have some changes in en-US.tmdl file that means nothing for me. I have no idea if I have to comiit then or I can ignore them.

    Any documentation woul be helpful here.

    Found nothing on internet.