PURVIEW | Sensitivity labels absent from the Office 365 suite La mise en place des étiquettes de sensibilités peut être très pratique pour classifier les documents depuis la suite Office 365. Pour cela, nous avons mis en place dans Purview, une étiquette et une stratégie pour affecter ces dernières à certains utilisateurs.Nos utilisateurs utilisent des… Continue reading PURVIEW | Les étiquettes de sensibilité absentes dans la suite Office 365
Bonjour à tous Hier un client a « planté » 350 utilisateurs pendant une demi-journée car leur suite Office 365 ne pouvait pas se connecter aux services Microsoft alors qu’étrangement ces derniers pouvaient se connecter depuis d’autre poste de travail aux mêmes services, via un navigateur. Après plusieurs investigations aux niveaux des services proxy qui n’ont rien… Continue reading MICROSOFT 0365 : Vérifier vos versions de TLS
I came around an interesting topic in the community forums where the issue was about the inability to delete a created table because of the dependency of type ‘app action’.
What is app action?
App action is created when you create a new command bar button using Power FX Formula and a component library gets created.
To demonstrate what this means follow these steps:
Create a table called Table 1
Create a model driven app called Test Dependencies Issues.
Add the table to your Model Driven app by adding a new page.
Click Edit command Bar on your Table
Add a new button and name it Test Command.
When you choose to create a new command of type powerFx formula you get the below message which means a new component library will be created for your button, Save an publish.
7. Now you can go to dependencies and check there will be a dependency on the Model Driven app and this is easy by removing button and the table from the model driven app and another dependency which is the app action.
How to get rid of this dependency?
This dependency is not available through the UI and so you need to use the Rest Builder tool to identify the Id highlighted in the above image and then delete it using the rest builder tool.
Open the Dataverse Rest Builder tool of the XRM toolbox, Perform a Retrieve Multiple Request on the Primary Entity appaction and click create request to view the results.
2. Identify the Id of the app action related to your table and then using the Delete action on the Dataverse Rest Builder , delete the app action and hence you delete the dependency.
Kudos goes to Prakash4691 and his awesome topic answer here.
I came around an interesting topic in the community forums where the issue was about the inability to delete a created table because of the dependency of type ‘app action’.
What is app action?
App action is created when you create a new command bar button using Power FX Formula and a component library gets created.
To demonstrate what this means follow these steps:
Create a table called Table 1
Create a model driven app called Test Dependencies Issues.
Add the table to your Model Driven app by adding a new page.
Click Edit command Bar on your Table
Add a new button and name it Test Command.
When you choose to create a new command of type powerFx formula you get the below message which means a new component library will be created for your button, Save an publish.
7. Now you can go to dependencies and check there will be a dependency on the Model Driven app and this is easy by removing button and the table from the model driven app and another dependency which is the app action.
How to get rid of this dependency?
This dependency is not available through the UI and so you need to use the Rest Builder tool to identify the Id highlighted in the above image and then delete it using the rest builder tool.
Open the Dataverse Rest Builder tool of the XRM toolbox, Perform a Retrieve Multiple Request on the Primary Entity appaction and click create request to view the results.
2. Identify the Id of the app action related to your table and then using the Delete action on the Dataverse Rest Builder , delete the app action and hence you delete the dependency.
Kudos goes to Prakash4691 and his awesome topic answer here.
I thought this might be useful to share , we run into an issue where we used the new command bar editor to create new buttons and All was good till we added a new column to the same table and published all customisations, went to the Command Bar and tried to set the visible property using Power FX formula but unfortunately the new column did not show up.
So by contacting Microsoft this is a known issue as of now and as a work around you need to follow the below steps:
Go to the Solution -> Choose the app ->Select the table -> Right Click Edit Command Bar.
3. Choose the Command Bar you want to Edit
4. Select your customised button and click Open Component Library
5. Component Library will be loaded on the Menu Click File -> Save , Then Publish and then reopen the Command Bar ,your metadata will be refreshed.
Connexion
