on
RE:
Until Microsoft provides such a functionality (not sure event if they will), you could use Parameters. I created 2 parameters for myself. One of them is a boolean and is called "LocalDevelopment" and one of them is a date called "LocalDevelopmentStartDate". I am using these 2 within my power query (advanced editor) to build dynamic dates for queries, filters so that I don't load all my dataset but only some that i can use to do local development. Once I publish the semantic model, I change "LocalDevelopment" parameter to False from Semantic Model settings and refresh the data afterwards. Since it is built in the transformation step, it will request all data in the server.
RE:
This is a much needed feature
RE:
I think it is important to have a feature that allows you to speed up inbound flows in intercompany transactions
RE:
Based on Finnish Tax law the acquisition date is not relevant for calculating depreciation even for the first year. Only the residual amount at the end of fiscal year is used to calculate Tax layer depreciation. This is currently not possible in D365 unless the user changes the Placed in service date manually after Acquisition. More information on Tax layer depreciation calculation in Finland: https://www.vero.fi/en/businesses-and-corporations/taxes-and-charges/limited-companies-and-cooperatives/depreciation-expenses/
RE:
The only way to think about the X axis in waterfall is currently to think about whether it is negative or positive compared to the value on the right side, so I need something like a switch that can determine whether it is negative or positive compared to the value on the left side.
RE:
For example of this issue see forum post: https://community.fabric.microsoft.com/t5/Desktop/Line-Chart-X-axis-Continous-Dates-add-time-stamp-when-there-are/m-p/4136193#M1304556
RE:
I support this. This is because if you create a file, you won't be able to get it out easily unless you have access to OneLake (this would be a solution for people having access to this app).
RE:
This should also work at the App layer, not just from reports in the workspace. Currently the sharing functionality is different for users of the app vs. members of the workspace.