on
RE:
@Nikola MIt is in the nature of things.see also here: https://vatdesk.eu/en/reverse-charge-mechanism/In the area of sales, only the assessment basis, i.e. the net amount, is reported to the tax authorities for reverse charge cases. This is why we in BC don't calculate VAT for this case and don't post any G/L entry for this. In purchasing, we have to report both the purchase VAT and the reverse charge VAT to the authorities. Therefore, we create a VAT entry and evaluate it twice in the VAT statement, once positively and once negatively. And we post the VAT amount in G/L as well:
RE:
Absolutely needed for various reasons, i.e. data validation of segments, export data to external providers (for white mailings, outbound telemarketing)....
RE:
Can do this in PIVOT tables, why not here as well? Please implement this change.
RE:
I think there's a lot of room to take improvements from VS Code to massively improve the online dev UX vs Databricks. I hope the Fabric team is paying attention to the devs, which are the main cheerleaders out there promoting tech products as they move between jobs, etc.
RE:
I do hope the Fabric team is paying attention to the improvements that Databricks is making ... they have a lot of catching up to do!
RE:
There are related proposals like this that I had ignored, but your note about leveraging this as a source for external tooling like Tableau is exactly how we are using this feature for one of our Databricks projects. It is also how Fivetran is pushing data into Databricks from several external data sources.
RE:
This is really strange to see that Microsoft doesn't support its own mainstream git provider, which happens to be the main place to find docs on Fabric!
RE:
How is this just "Under Review" ... hopefully my comment makes no sense to future readers in the very near future! :)