Related to error message "Resource not found for the segment" From MS Documentation: This error occurs when you use the incorrect name for a resource. That resource might be the name of an entity set, a function or an action. These resource names are case sensitive., there is an entity set called accounts, but not one named Account etc. Below are things that can be verified: Check the URL to make sure the environment and versions are correct Validate the Action name Check in the actions section in Solution if it is available. Check in the WebAPI metadata if it is available Make sure all customizations are published in your solutions. Validate the WebAPI accessibility with the System Admin user role Hope one of them would resolve.
Posts
Resolved: Retrieve all users while using 'List group members' Action | Office 365 Groups Connector | Power Automate
By default, the 'List group members' Action in Office Groups Connector returns only 100 records and you might not find the desired record in the returned list. Resolution: Increase 'Page Size' Turn on the Pagination and Increase Threshold in Settings of Action.
Resolved: Add User to Group and Check If already Exists | Power Automate | Office 365 Groups Connector
The context of this blog post is to add the AD Users into Office 365 Groups using Power Automate Flow. For one requirement, when I was trying to implement I experienced the below error and thought this post would be helpful for someone in future encountering the same issue and would save some R&D time. Error: One or more added object references already exist for the following modified properties: 'members' Understanding the above error: When a user is already present in the group and we try to add him again using the 'Add member to group' Action of the Office 365 Groups connector we will get the above error. Resolution: We can check beforehand if the User is present in the target 'Office 365 Group' or not and add if not already present. How To:, Below is a snapshot of Power Automate flow should be self-explanatory Use the 'List Group Members' to check if the user already exists and apply a filter to check for the existence of the required user record
This blog post is just to make sure, whoever is searching for accessing environment variables don't get the old way of retrieving the variable using dataverse connector connecting to the 'EnvironmentVariables' table and retrieving data. With the latest update, now we have direct access to 'EnvironmentVariables' in the flow. In any of your input fields, just focus on that, you will see the 'Environment Variables' in the context menu. Most of the Power automate developers will be rejoicing with this update!
Is PowerApps Portal fully dependent on DataVerse Storage to store data? Earlier the answer was yes, as Power Apps Portal was tightly bound to DataVerse. Now with the CRUD support to Virtual Tables (Entities), we can easily configure an external database with a custom data provider and make Portal to use Virtual entities for Making CRUD operations from Power Apps Portals. Follow below article to create Virtual Table and configure that to an external SQL database Sample: Custom virtual table provider with CRUD operations (Microsoft Dataverse) - Power Apps | Microsoft Docs Once Virtual Table setup is up and running, set-up portal instance on same environment and start creating Form (Entity Form), List (Entity List), WebPages as usual. Be amazed to see how seamlessly the integration happens between portal, virtual entity and the external data source. Below is the data flow Some screenshots: Enabling the CRUD operations on Virtual Entities has provided many more options to explore from the
The most awaited feature for Power Apps portal is now available in public preview... This will open up lot of unexplored space in Portals.. Much needed and will be most used going forward. Below are the functionalities available in public preview Create Update Delete Associate and disassociate More details in below link: https://powerapps.microsoft.com/en-us/blog/power-apps-portals-web-api-support-public-preview/
[Resolved] XRMToolbox - An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
To keep this post short and simple. Trial instance which I created has MFA has been enabled and while we are using the old method of login into XRMToolbox via Connection wizard, we are getting below error, as there is no possibility of a second level of authentication via Mobile. Below is stack trace and error encountered: Error : An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. Stack Trace : Server stack trace: at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, P