Also you can still switch to iam using the application switcher at the top left.
To see this menu item the user needs to be a developer in IAM. However, this feature is not yet available outside the Thinkwise domain. There is still some work to do to make this feature available. That's why you can't see it even with admin rights.
Pardon me, you are right. Here is the main information: The export in universal always shows pks. This is needed to be able to re-import the dataset later on. Are the columns you're seeing pks?If you hide a non-pk column (in subjects in the tab columns) it should not be visible in the export.
Please check this topic if this answers your questions:
@Harm Horstman we fixed this problem, it's now possible to download hotfix only using the universal gui.
This is a known issue we are working on a solution. In the meantime you can still use the webgui to download hotfixes only. https://tcp.thinkwise.app/web/Default.aspx
Did you check the indicium log?
The problem with offset is the higher the number becomes the slower the query. This means once you reach the last page the performance will take a dip. A few questions you could ask from a user perspective. do you need to see 6k of rows, or could you apply some filtering to limit this? Is the sorting order correct? Could you apply some manual filtering? Also did you check the execution plan if there are any missing indexes?
This is an error in the application please report this as a ticket in tcp. I will therefor close this topic.
@Blommetje did the hotfix solve the problem?
Since this is also reported as a ticket I will close this topic.
This is currently not possible. Feel free to create an idea for this. If you do, please make 2 separate idea's. One for the bold text and one for the column width adjustment.
@groos did Mark or rbiram's replies answer you question sufficiently?
@AlfonsM did Arie's suggestion answer your question?
Since this is also reported as a ticket I will close this topic to keep the communication centralized.
I asked around but we don't really have an explanation for this. If a user who has a working profile logs onto his system do they then also experience this problem? Then it might be a problem on the work station it self, and not so much the account.
I tried with a date data type, also tried with several language settings, both iam and gui. It all works like supposed to. Perhaps it would be best if you create a ticket for this and add a model extract. Then we can check if we can recreate with your model.
Is there a difference in control type/date format (data type) between the ones that do and don't work?
And the version of the platform (sf/iam version)?
This is not on the backlog and this behavior is by design. So indeed you need to take this into account when creating an application. Feel free to create an idea for this in the ideas section.
It seems you only have included columns on the index. This is not allowed. There should be a validation to prevent this (I will create an idea for this). When creating an index you need at least 1 column where included is not ticket and you can add as many included columns as you like (but adding too many is not a good thing).
This is currently not possible. Why not use a multiline control?
Hello @Tejo van de Bor tried in 2022.2 still works like a charm. Seems like we are missing a key element here. Are you planning on upgrading this environment in the near future? If not you could report this as a ticket but we would need a software factory backup to investigate this.
Are you using the same credentials in postman and in the process flow?
Which version of the platform and gui are you using?
Already have an account? Login
Enter your username or 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.
