on
RE:
I think users will be able to see and connect to the linked entities only if they have access to both the staging workspace and the transformation workspace. Which is quite nice. https://learn.microsoft.com/en-us/power-query/dataflows/linked-tables#permissions-when-viewing-reports-from-dataflows. "When creating a Power BI report that includes data based on a dataflow, you can see any linked tables only when you have access to the source dataflow."
RE:
I think you can rename the linked entities in the transformation dataflow. So you could prefix them with "linked_" or something. Also, I think users will be able to see and connect to the linked entities only if they have access to both the staging workspace and the transformation workspace. Which is quite nice. https://learn.microsoft.com/en-us/power-query/dataflows/linked-tables#permissions-when-viewing-reports-from-dataflows. "When creating a Power BI report that includes data based on a dataflow, you can see any linked tables only when you have access to the source dataflow."
RE:
I think users will be able to see and connect to the linked entities only if they have access to both the staging workspace and the transformation workspace. Which is quite nice. https://learn.microsoft.com/en-us/power-query/dataflows/linked-tables#permissions-when-viewing-reports-from-dataflows. "When creating a Power BI report that includes data based on a dataflow, you can see any linked tables only when you have access to the source dataflow."
RE:
A lot of companies, customers of Business Central are using the deferral function. The deferral function is immediately linked to Revenue (and expense) recogntion. Each company is closing their financials, monthly, quarterly or yearly. It happens that certain contracts, subscriptions need to be posted (expense or revenue), while the period is closed but the starting date of the subscription is before the closing date. But you can, may not change the financial results for closed periods.Example: Fiscal Year End - 31/12/23, and the period is closed for Jan '24.Customer needs to be invoiced in February 24 for a subscription starting 1/10/23 to 30/9/24, for 12.000 Euro (1.000 Euro per month).Accounting wise, we need to recognize revenue in February 24 - 4 months * 1.000 Euro = 4.000 Euro, and 8.000 Euro is deferred. Starting date 1/10/23, of the subscription Posting date 15/2/24, and 4 months needs recognized as revenue, 8 months need to be deferred.Current standard, wants to recognize revenue at the starting date - 1/10/23 - but the period is closed.
RE:
One of the many sorely missing features in Power BI :)
RE:
Hello Geeta, thank you for posting this idea. Even I get queries from my clients why we cannot attach multiple files. They have quotations, images, policy documents, T&C file to attach on every single orders for few specific customers. And doing one at a time is not user friendly. This feature should be rolled out asap.
RE:
this is a huge problem for us.... confusing to our customers. and the date can reflect the report update and/or the actually underlying data update..... please turn off for individual reports!!!!
RE:
Link - https://experience.dynamics.com/ideas/idea/?ideaid=20564e8d-b074-ef11-a4e5-6045bdb6aac7Microsoft has introduced a new feature called "Configure POS Self-Checkout Register" in version 10.0.40.By enabling this feature, retailers can now utilize Microsoft’s built-in self-checkout functionality on Kiosk POS systems. This has been a highly anticipated update, as many users have been waiting for this capability.However, an existing feature in POS, which allows users to click on the "Amount Due" link from the "Total" panel to display all available payment tenders, has presented an issue for the Self-Checkout setup. While this behavior is intended for normal POS counters, it poses a problem for Self-Checkout kiosks, which should only support "Card" and "Loyalty" payments, but not "Cash" payments.Currently, there is no way to restrict certain payment tenders specifically for Self-Checkout kiosks, especially in stores that have both regular POS counters and Self-Checkout kiosks. As a result, customers can still make cash payments at the Self-Checkout, which is not ideal and creates a loophole in the system.
RE:
Related idea: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=ab3d20d2-acd4-4355-8889-415c0bc609ab
RE:
The linked refresh behaviour leads to data in a transformation dataflow getting out of sync if there are two parallell staging dataflows (which is a common setup). I really wish there was an option to disable linked refresh. https://community.fabric.microsoft.com/t5/Service/Dataflows-Linked-entities-refresh-issue/m-p/4153007