cancel
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Status: New
Status: New
Status: New
Status: New
Status: New
Status: New
  • Admin Tooling
Status: New
Status: New
Status: New
Status: Under Review

For environments in government cloud, starting an AI Builder trial has been disabled.

We are going to include some AI Builder capacity with Power Apps licenses soon.

AI Builder trial will be disabled for these tenants.

Ability to totally disable AI Builder trials even for tenants with Power Apps or Power Automate trial is not planned yet.

Status: New
  • Admin Tooling
Status: New
Status: New
Status: New
Status: New
Status: New
  • Admin Tooling
Status: New
  • Admin Tooling
Status: New
Status: New
Status: New

Thanks Jitendra for logging this idea. I am adding few more details with screenshots so that it would be easier to relate the differences in terms of querying entity relationship data over API from CRM and Portals. 

  • An N:N relationship was created which then created a relationship entity --> new_passengercarriers

 

saurabhtiwarii_0-1636971137160.png

 

 

  • Created sample records on these two new entities and then associated some records.   

 

  • When one queries over the DB for the contents under this table, we can see that it includes only a few columns relevant to the two entities record associations.
     

saurabhtiwarii_1-1636971137166.png

 

 

 

  • This whole relationship table data can be queried over the CRM web API by suffixing “Set” within the logical name of the relationship entity.


Example Relationship Entity name :: new_passengercarriers

Query over the web API ::

https://MyOrgURL/api/data/v9.1/new_passengercarriersset

saurabhtiwarii_2-1636971137177.png

 

But there is no way to expose this currently over Portals web API since the relationship table is not available for use within entity permissions.

Labels