For windows gui also please ;-)
Thanks @Mark_Plaggenborg, was looking for ‘buttons’ in documentation where ‘icons’ was the trick.
hi Mark,In this case I have a processflow starting with a table task, getting the specific row in a new status: And I understand that the refresh at the end of the process (or any gui handling) can be interrupting the process, but then at least it is a choice for the developer.
hi @Jeroen van den Belt I guess that Erwin’s solution is the best of the rest, as multi row execution is taking a few extra steps that should not be needed. As for instance, I’ve to create looping in my processflow that should not be necessary cause normal tasks can handle this already.Created an idea here to upvote 😀
hi @Mark Kroes, still need some support on this. It’s not blocking development this moment, but it should work right?
hi Mark, I understand, but in the 2 years we’ve been developing with Thinkwise, this has been a promise and there is no release date yet.
Afterburner: I added some extra scripts in the badge for adding a message:But a bad reference to a view 😬 (oops) broke it. The error never showed in debugger, that’s strange right?
Don’t know what the reason is, but the BADGE is now suddenly present on the view tab 😳So maybe the deployment fixed things I don’t know of, or the 10th time Indicium was restarted fixed this, but glad it’s working now.
The badge is on a view, shown as a detail tab in Windows GUI. Validations (table shipment_validation) has a working badge, Communication log is a view but the BADGE is never shown in the debugger.
Yes, the one on General I set manually and the other on Performance was set by adding the code group Batches to this view.
Ah, its because of the capitals? No, it didnt crash, but if I see a warning message I want to know if it’s going to give trouble in the project ;-) So it’s only the preferred naming convention.
hi @Erwin Ekkel, we use 2022.2I have a base project with several tables, columnnames are translated. Added the base project, and generate definition for the work project The translation objects are there, but not the translation Any tips?
Thanks @Vincent Doppenberg , I added the change detection and this works for now. For the button I added a check in the task if an earlier request already has been sent. Maybe an extra field with some in-between-status information so the user sees something happing when clicking the button :-)
hi Mark,We checked the screentype, it has a Tiles component with Detail group A, and in the subjects we added the Links-Details-Detail group, 2 tiles with group A and 1 tile with group B. Now all 3 tiles are shown, why is B also shown? Is there a way to check why this is not working? In our Insights demo we see exact the same configuration, and working.
jep, found it, typo in task name. Grazi!
Hi @Mark Jongeling, any thoughts on the message “The MERGE statement conflicted with the FOREIGN KEY constraint "ref_prog_object_prog_object_item". The conflict occurred in database "SF", table "dbo.prog_object".” when generating definition?Even with the default code when creating a new procedure.I’ve added project_id and project_vrs_id (seen in examples with Delete strategy) but this doesn’t helpadded task control procedure: changed default codeusing 2022.2 up to hotfix 20230313
1 final question, how do you get the initial copy_to_id? in our case these are identity seeds, so when inserting the details, I have to use the main table’s id. Is there a Thinkwise ‘trick’ to get this one? Or just use the @@identity?
ok, getting the vibe here! I added the c.include_in_copy=1 when getting the columns.
thanks, I see now how the many task_copy procedures are created in SF! Some homework to do here.
ha, that’s inspiration allright 😳 I’m gonna spell it out word by word to understand and get back to you, thanks!
Thanks Mark, I didn’t know the ‘underscore’ tables could be part of the model, thought they are more under the hood parts :-) Can there be a validation that triggers this kind of faults in the model?
hi @Jeroen van den Belt , I think that the formlist is a rather complex solution for something that could be easily fixed if the translations for those extra fields could easily be changed for the endproduct in a ISV customers’ environment.But I guess that is not supported at this time? To change translations in IAM or better still in the endproduct?
hi Mark, thanks, I’m gonna look into that. First enjoy the weekend and your holidays, cheers!
hi Mark,When joining other tables in the view, the form is not updatable. Error “View or function 'shipment_view' is not updatable because the modification affects multiple base tables.”how can I handle this? With instead of triggers?Do I really have to address every field (+/- 80) in the statements? When I read your first comment, I thought it was a simple change :-/
ok, I see in the copied subject, there are also some fields not copied e.g. the custom-lookup and the display column. So it’s not a flawless process :-) but I think all procedures and processflows are changed now for the view.
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.
