Tabular Editor 3 is fantastic. One interesting 'save' that it provided me was the ability to edit the server name in the connection string for a cube published to a deployment pipeline. Promoting the cube from the dev to test or test to prod workgroup carries the server name from the lower environment forward. The connection cannot be updated via the web interface but can be using Tabular Editor! Macros for generating measures is also fantastic. Select all your implicit measures, run a macro to build DAX measures and hide the implicit ones.
I would make sure to note that "Direct Lake datasets created or modified by using XMLA-based tools cannot be opened in the Web modelling feature" as that might be of concern for some people
@@remek5758 I tried using it yesterday and ran into a problem where I needed to update my model but now that I cannot utilize the online interface have to either purchase TB3 as TB2 does not have built in functionality to create new tables or direct lake datasets. You have to do this manually or with c#. This to me for new people experiencing modeling in fabric and are learning from tutorials could be a problem when they find out.
I've tried the tool today, but it has limitations. If you edit a web based semantic model, any change you make to a table, automatically makes that table to fallback to Direct Query and thus, the warning icon appears on them when published. There's no way to change it back to Direct Lake. Also, after you use TE3 to modify a semantic model, it can't be modified online anymore. I wanted to use this tool to make a copy of a web SM, but this limitations are a no go for me.
What is the best way to manage the data once it is in the Lakehouse? How do we easily insert\update\delete the data? I would prefer not to have to go thru a bulk insert every time. Thank you
Question: I have 5 visuals on powerbi Dashboard. Each one of them has a visual level filter related to different DATES criteria. In order to get an updated weekly report i have to change the dates on each visual every week, Is there any smart way to use only one filter and change all the visual level filters w.r.t DATES (keeping the filter criteria of each visual as intact). Thanks in advance for any answer.
May be I don't understand your problem, because I don't understand why you have to set a date filter manually every week instead of using relative date filters or precalculated values at your date dimension, which could be used for filtering date periods. May be, you could share more details?
Q: Is it also possible to create field parameters for attribute sliders with tab editor in a direct lake dataset? Right now it is the only feature which I don’t know how to migrate from my old big dataset to my new direct lake dataset.
Q: We tried to change this settings (implicit measure) with TE2.2 on our "default" "Warehouse" and "Lakehouse" (Fabric) dataset, but we got an error that the object either not exists or we don't have enough permissions to do this. (We could connect to these default datasets, change the setting, but if we save, we get this error). We are Workspace Admins. The warehouse/lakehouse(s) were created by us. XMLA read/write is activated at our capacity. (we could change the settings of a "normal" import-dataset in this workspace). What could be the reason for our problem?
Lol, we tried this for days and I just send my question here and found my answer by myself: "Note that XMLA Write operations are not supported with default datasets. You must create a separate Direct Lake dataset, sometimes called standalone or custom dataset." I don't delete my question (better for the yt-Algorithm and may be someone else has the same problem) 😂
