Daniel Khalil

• virtual entities only work with the highlighted options on the connection:
• Azure AD integrated
• SQL server authentication
• windows authentication
• service principale
• The windows ones are for On Premises , so that leaves us with AD integrated and SQL Server Authentication.

so we can conclude that using the clientID/secret doesn't work with Virtual entities for cloud environments.

the connection can be created but cannot be choosen when creating the entity.And on changing from the inside it doesn't connect and returns null data.

would like to be able to select the created ClientID/Secret connection when creating virtual entities.

for saved views in workspaces, in order to publish a view with pinned elements.

you need to publish the backing views before adding any pinned elements.

You need to remove the pinned elements, publish the backing view for those elements first, then recreate the elements again.

this is quite a manual task for each saved view in a workspace.

the "Saved views support for workspaces" feature further developments should work on having this process automated, rather than having to publish each backing view, before adding the pinned elements.