Hello @Vincent Doppenberg,You are absolutely right. I made a slip of the pen. After correcting this I found that one particular value does not exist in the request (anymore). After removing that value it works again.Thank you for your response and your help!
As an addition to my post: I have now set all the columns I don't want to show up as duplicates to hidden in the data model. Only to my surprise it does the following:The columns I set to hidden in the data model are simply unchecked. This happens with both tables and views. I expected them to be hidden. So instead of the columns being hidden, they are only unchecked. This is not what I expected and wanted, as it might still confuse our users. The checked columns are the visible columns that shows a converted and formatted value and the unchekced one shows the data we save in the database.
Hi Mark,Thank you for your help. I found the problem, I apparently set in the where clause that only visible columns must be used to create the new columns. Seeming that I already use a column tag to filter out the columns that I need, the conditional clause on visible columns was a bit redundant. Now that has been removed and now it works just fine.Again thanks for your help, as it helped me find the problem by searching for rights and where they were set and possibly edited 😃
Hi Mark,I can try to update the roles of the columns I want to update (so they will be hidden in the data model) to see if the error goes away, but that does not explain why it goes right once, and doesn’t give me an error immediately. Is that because in a staged strategy the first update of these columns they do not have to be deleted? That would make sense and explains why it goes wrong the second time.I am trying to update, non generated, existing columns. The generated columns are based on these columns. The generated columns go well, these are used for display purposes, but the actual, existing database columns need to be hidden so they won't pop up in the export list.
Hi Mark,We made an API-key on an organization account. So I think that got configured correctly. I understand that it is awaiting responses, and I understand that it could take long(er), but that does not explain the problem where it freezes and get stuck at around 25% completion. If this did not happen, I would gladly wait a few hours for it to complete, in the meantime I can work on something else.It should not be necessary to process as much data, but seeming we are migrating our manual test cases to the SF, it is necessary now. It works fine but slow, until it freezes. So could it be default OpenAI behaviour to freeze all requests if a limit is reached, or should it continue after a bit of cool down. Because I do not think the freezing makes sense.
Hi Mark,Thanks for the response. That idea indeed does cover what we need in this case.So if I understand it correctly, the database values, even when hidden in the subject, are displayed at export? If that is so, we may be able to make all non-display fields hidden in the model for the time being, so we can exclude the fields from the export list.
Hi Mark,We are using the universal GUI. In this case it is necessary as the pop up opens far to small. Just one or two items can be shown on that window when it is that default opening size. For user experience this is not optimal, that's why we ask that a minimum size can be set, so the items can at least be shown in card or grid form. Now it just opens a window as in the following screenshot, without an option to edit it without affecting all other windows: This means our users constantly have to expand this screen to a grid screen size to drag and drop the names onto the items in the screen it is opened in. This is inconvenient for both user and programmer.
Hello groos,That option has been discussed in my post. It is the option I do not want to use, as I will make a general size for all windows and pop ups. That is not my intention. I want to be able to set a size for a specific window, in this case, the window I am currently letting appear for functionality I am working on. So it would be nice that the size can be set per pop up or window.Kind regards,Sander Adam
I eventually solved this by adding the start up contidion as a clickable task. Like that I could emulate a start up. Now the thing I wanted to add has been added and the task has been deleted.
Hello Boudewijn,the startup task in question is a task we developed ourselves to help the user set up some first data. This task is set per user in the IAM. Since the software factory is run without the IAM settings and roles/rights, we are unable to simulate this task in the Software Factory.Now we need to add a parameter for the user to set, so we need to be able to debug it. But that is difficult when one cannot debug. We need to emulate the startup task set to a user in the IAM, so we can debug it and see if everything is done right. I hope that makes my question a bit clearer.
I can't reproduce this. Are you using any custom css for the universal gui? We do use custom CSS, but as far as I know not for this field with the load bar. We do use it to colour certain buttons and other elements red (mostly for emphasis).
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.
