Reuse tmdl scripts

[thod]

Hi,
I have created a TMDL script snippet (a formattet calendar table, eg. created spaces in column names) that I want to reuse in other models.
When I create a new model, implement the script and click apply in TMDL view, the formattet table shows up. However, when I refresh the model within Power BI desktop, the table reformats to the source column names. I then need to go back to TMDL view and click apply again.
Am I doing something wrong so it can be avoided?
My test script is:

createOrReplace

    table Dato

        lineageTag: 5f8716ac-005a-405d-8f55-d40786b53a72

        dataCategory: Time

        column 'Dato Tid Fra'

            dataType: dateTime

            formatString: General Number

            lineageTag: ffb6bdc2-5ade-4339-b5c3-ecbfd92a113d

            dataCategory: Uncategorized

            summarizeBy: none

            sourceColumn: Dato Tid Fra

            annotation SummarizationSetBy = User

        column Dato

            dataType: dateTime

            isNullable: false

            formatString: Short Date

            lineageTag: 05acc131-b6b3-498f-b998-010145dfcb45

            dataCategory: Uncategorized

            summarizeBy: none

            sourceColumn: Dato

            annotation SummarizationSetBy = User

        column DW_SK_Dato

            dataType: int64

            isHidden

            isNullable: false

            lineageTag: 7cb8437a-3dda-4290-88cd-443305dc0b03

            dataCategory: Uncategorized

            summarizeBy: none

            sourceColumn: DW_SK_Dato

            annotation SummarizationSetBy = User

        partition Dato = m

            mode: directQuery

            source =

                    let

                        Source = Sql.Database(Server, Database, [Query="/****** Script for SelectTopNRows command from SSMS  ******/#(lf)SELECT [DW_SK_Dato]#(lf)      ,[Dato]#(lf)      ,[DatoTidFra]#(lf)  FROM [DSO_SharedDimensions].[all].[DimDato]"])

                    in

                        Source

        annotation PBI_NavigationStepName = Navigation

        annotation PBI_ResultType = Table

[MFelix]

Hi @thod ,

This functionality was just released in the new Power BI desktop version of May. So you can now if you rename the columns the values persist without the need to have a step on Power Query.

[v-pbandela-msft · Accepted solution]

Hi @thod,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please "Accept  as  Solution" and give a 'Kudos' so other members can easily find it.

Thank you,
Pavan.

[v-pbandela-msft]

Hi @thod,

Thank you for reaching out in Microsoft Community Forum.

Thank you  @MFelixfor the helpful responses.

As suggested by MFelix,  I hope this information was helpful. Please let me know if you have any further questions or you'd like to discuss this further. If this answers your question, please "Accept as Solution" and give it a 'Kudos' so others can find it easily.

Please continue using Microsoft community forum.

Regards,
Pavan.

[MFelix]

Hi @thod ,

This feature is still on preview, I believe that what is happening is that since you are applying the TMDL on top of the table you have on your model, it does not create the additional step of the rename in M language causing it to not recognize at the first run.

I would send this to the feedback form

https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR63OJ8qKvQlMm9JxH0flWGRUM0E4...

https://powerbi.microsoft.com/en-us/blog/deep-dive-into-tmdl-view-for-power-bi-desktop-preview/

[johnt75]

This could be a bug, especially as its still a preview feature. I'd use the "Submit feedback" button in TMDL view to let MS know.

As a workaround you could do your column renaming either in SQL or in Power Query. That should get picked up and remembered when you do a refresh.

[thod]

Yes, I already gave the feedback. Just wanted to know if anyone here had experienced the same thing and found a solution 🙂