Page https://docs.tabulareditor.com/te2/Advanced-Scripting.html and https://docs.tabulareditor.com/te3/features/csharp-scripts.html both refer to Appendix A, which doesn't seem to exist. I'm guessing it's a work in progress? Is there a workaround until the doc is created?

Shouldn't the Github link be updated to https://github.com/microsoft/Analysis-Services/tree/master/BestPracticeRules in the following docs?

• The last paragraph.
• The last paragraph under "Adding additional collections".

https://github.com/TabularEditor/TabularEditorDocs/blob/main/te3/tutorials/incremental-refresh-about.md

claims that incremental refresh requires query folding. While desirable, it is not required. You can achieve successful incremental refresh with custom queries as well if they incorporate the RangeStart/RangeEnd parameters. Dataflows can also do successful incremental refresh of file data based partitions (these may not be as efficient though).

Hej

Den er død:

Mvh - Henrik 😊

in this doc it could be useful to add an example of Power BI connection string with SPN as done for AAS.
https://github.com/TabularEditor/TabularEditorDocs/blob/main/te2/Command-line-Options.md/#command-line

Probably the most common blocker for this process would be if the XMLA endpoint has already processed the incremental refresh policy and created the numerous partitions. PBID will not allow you to open and rehydrate a file with policy based partitions (or any tables with more than one partition).

So we need to remove the policy based partitions, and create a new M partition with the incremental refresh expression. Here's a script that I am using to do this, and it looks like it's allowing me to proceed with the rehydration.

foreach (var t in Model.Tables)
{
    if(t.EnableRefreshPolicy)
 {
    //We will collect the SourceExpression from the Incremental Refresh Source Expression of the table
    string m_expression = t.SourceExpression.ToString();
     
    //We will generate a new partition name
    string partition_name = t.Name + "-" + Guid.NewGuid();

    //Now we will create a new partition
    t.AddMPartition(partition_name, m_expression);
    
    //Next we will delete all the incremental refresh partitions of the table
    foreach (var p in t.Partitions.Where(p => p.Name != partition_name).ToList())
    {
        p.Delete();
    }

    //Next we will set this M partition to Import mode
    foreach (var p in t.Partitions.Where(p => p.SourceType.ToString() == "M").ToList())
    {
        p.Mode = 0;
    }
     
}
};

Anyway someone better than me can improve that code and get that added into the documentation to help assist?

te3/features/deployment.md is incomplete. Came here looking for the details of each of the deploy settings (more specifically, what happens during deployment when you select Deploy Table Partitions) from here: https://docs.tabulareditor.com/te3/features/deployment.html

Wouldn't it be helpful if a clear list of Power BI plans that support Incremental refresh had been provided? Even Microsoft themselves get confused if asked this question.

clicking on an image only shows a larger image :)