Power Platform Governance and Administration

Please allow customers a read-only replica of a SQL server endpoint for Power BI reporting. The current implementation of Synapse Link is not working properly, and has many issues and bugs. By allowing a read-only replica you will make it easier for customers and for yourselves. What is the primary blocker of allowing said replica to exist?

Improve the inconsistencies and gaps in the data in the Power Platform Admin Center downloadable licensing reports.

See: TrackingID#2404120040012099

I tried to view my credit statis in Power Platform admin center > Resources > Capacity > Addons > AI Builder credit.

However it was hard to understand.

It shows: (Originally in Japanese)

---------------------------------------

AI Builder Credit

0 / 1 が割り当て済み (0 of 1 assigned)

145 / 1 を消費しました (145 of 1 consumed)

---------------------------------------

I can't see that I'm consuming unassigned credits? Am I over using?

I think I choose Yes when "AI Builder credit extension to unblock an environment in overage" appeared.

So I think I have 200,000 credits for preview use.

I don't fully understand credit consumption rule, I can't see what credit is used for now. I'm afraid I have to pay $500 for 145 credits use? or I'm still in free zone?

Thanks.

Watanabe

There is a major issue when we try to render lookup fields as dropdowns using advanced form metadata. Let us say there are contact lookups. If contacts in an environment are more than 5000, we run into a platform issue as below:

Requirement:

Load an advanced form which is loading an account form tab at the backend. It has got couple of contact lookups primary contact and the billing contact. The contacts need to be filtered by corresponding account's contacts as well as parent account contacts which is not possible by out of box view. hence custom script was used to filter the contacts after rendering lookups as dropdowns via advanced form metadata.

Issue:

If you load corresponding advanced form step in power apps portal, if you select a contact which is among the first 5000 contacts in alphabetical order (a-z), you will be able to press next button and proceed without any issues. But if the contact you selected in that lookup (rendered as drop-down) is beyond first 5000 contacts then you get a platform error and unable to proceed.

I had raised Microsoft ticket with number 2402210030000524, where I shared recording for the issue as well. Happy to be contacted at akshat.gode@brennanit.com.au for any queries related to the issue.

Also power-apps portal does not support out of box lookup filtering where 1: many relationships is involved, which is otherwise supported by dynamics.

We had to do workarounds in user journey to be able to accomplish above requirement and get clients agreement unfortunately because of given product behavior.

We want this product behavior fixed so that lookup filtering in power-apps portal can work seamlessly, without any issues.

We have the possibility to filter the lookup by related rows

You can filter this lookup column based on a row related to both the current table and this lookup.

Select a relationship from the Related row to current table first, and then select a relationship from the Related row to this lookup's table.

(https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/special-field-properties-legacy?view=op-9-1)

It would be awesome if we could have the same thing on subgrids. Show not all and related records, but also filter them by any lookup value that is present on the form.

Dear Microsoft Team,

I hope this email finds you well. My name is DEEP SHRESTHA, and I'm currently based in Australia. I'm reaching out to share an exciting idea that I believe aligns with Microsoft's commitment to innovation and enhancing user experience.

I envision creating a revolutionary website that offers users a seamless and secure way to access their desktop environment from anywhere with an internet connection. This website would function as an online operating system, allowing users to log in securely with unique credentials.

Once logged in, users would have full access to their desktop, applications, and files, eliminating the need to carry around a physical computer. This online OS would not only streamline accessibility but also provide flexibility and convenience to users worldwide.

Moreover, I propose integrating Microsoft apps seamlessly into this platform, ensuring a cohesive experience for users. The pricing model would be flexible, allowing users to choose their desired processor, RAM, graphics card, and storage capacity through a yearly subscription plan.

I believe that this concept has the potential to revolutionize the way individuals interact with their computing devices, making computing more accessible and convenient for everyone. Additionally, leveraging Microsoft's robust server infrastructure would ensure reliability and scalability for this innovative platform.

I'm eager to discuss this idea further and explore potential collaboration opportunities with Microsoft. If this proposal resonates with your vision and objectives, I would appreciate the opportunity to connect and discuss the next steps.

Thank you for considering this proposal. I look forward to hearing from you soon.

Best regards,

DEEP SHRESTHA

Enabling quick create allows us to see the create form on right side panel staying on the same page where we can see Parent Entity record details. It can be N number of entities where we might be using quick create functionality. It’s a good feature.

But it’s also allowing user to create directly from the Application Ribbon (global buttons) by default.

Which can generate issues like:

1.     Can end up showing N number of entities in the List, which is unnecessary, can not let us have clean UI.

2.     For some scenario, where Lookup is getting value by from sub grid context and hidden on form, addition of new record from Top Application Ribbon will create an orphan child record.

This should be configurable that what entities we want to allow to utilise the quick create from the Application Ribbon.

For example, as in the entity property itself should be a flag field which can be On/Off just like enabling Quick Create feature for the entity.

tags: Dataverse, Application Ribbon, Global Buttons, Quick Create Menu, Entity, Hide, Show, Enable, Disable, On, Off

When Microsoft is expiriencing system breaks, they should allways inform customers, not just "som known issues!

According to Microsoft Support:

______________________________________________________

Hello Thomas,  

This error that you have got is from the outage that we had all over and it is not a problem in your ORG, however it is related to package in power apps or you can say a call stack and Stephan, as you asked for an ID unfrotunatley there is no specific ID for external use as this is a known issue and as mentioned this was global issue which was fixed by PG team, now in these scenarios we don't create any specific document as these issues can happen once in a while (may be once in a year) and we just share the details with client about the outage or the work that's been done.

some known issues are reported in admin portal as well, so once you login to power platform admin centre, there is a section called as known issues, which you can always refer.

______________________________________________________

I am concerned about the lack of specific documentation or an ID that could be referenced by clients externally. 

The suggestion that such global issues might occur "once in a while" without formal documentation or public advisories does not align with the standards of accountability and professionalism we expect from you, especially given the critical nature of these services to our business operations.

It would be great if we could migrate the audit log from a source environment to another one.

If we have a copy from a source environment,, and later on, after the copy, if we need to copy the original audit log files it´s now possible. It would be great if we could do that, using a data flow or something similar.

Many organizations rely on external experts or partner companies to help manage and optimize their Power Platform environments. Currently, guest users in an Entra ID tenant can switch tenants and access (existing) Power Platform environments. Guest users cannot (yet) access the Power Platform Admin Center, which is necessary to manage environments. This restriction leads to a need for having (additional) member users with seperate licenses assigned, resulting in unnecessary costs for customers, as well as inefficiencies due to needing seperate identities for different customers.

I suggest that administrative capabilities can be enabled for guest users within the Power Platform Admin Center.