Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Good to hear. Glad that you are working on UX improvements.
Just a comment here. This is a fundamental functionality which need to be in place before we can consider start using Charts. We have one team which consider if it’s sufficient for their usage of time series visualization. Not sure if you and @Ola Øyan had a chat, if not we should follow up after Easter.
They seem to be public. But note that the UI is different between the login versions:OIDC:legacy: On OIDC I cannot see “Owner” and “Access” and “make private”. Is this related?
Creating the transformation in Fusion,both in OIDC and legacy login. Have not tried in the SDK. I can only delete it if I use legacy login with the group “transformations” added. No dataset scoping on the transformation capabilities. Yes, the group “transformations” is completely empty.If I remove the WRITE capability on the AAD group in OIDC I get the error message in Fusion: “Subject does not have 'WRITE' action in this project.”, while if I have it there is a different error message: “Transformation not found. This may also be due to insufficient access rights.” I also tried deleting the “transformations” group without giving any difference.
Hi.On the project “test”, there is a transformation: id:40, external_id:transformations_test.I am member of a group “IT-Rolle-CDF-Test-Admin” (with syncs to Azure AD) with the capabilities transformationsAcl:[READ,WRITE].I am able to create a new transformation both on legacy login and OIDC, meaning that the WRITE capability is available, but my service account needs to explicitly have access to the group “transformations” in order to delete or edit a transformation.The group “transformations” is empty without any Source ID or capabilities.
Until now this has been relevant when we have created a duplicate data set by mistake, or don’t need an empty data set.So for a minimum feature request it would be nice if a data set without associated data would be possible to delete.
Hi, I created the suggestion here: Anders
Hi, thanks for the reply.I tried using Fusion, and the error is due to the requirement of both a name and description. When the description is empty (NULL), the error occurs. A better input check in the frontend should be implemented to fix this. Even though there is an asteriks (*) after description, its not that easy for an end user to understand the error message. Thanks, Anders
Hi Kevin,thanks for the reply. Please keep us updated if there are any updates on the functionality.Anders
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.