Hi Carlos123,I was able to observe this error while building a simple screen. In my case, it occurred when the search section had a field in the search filters area, but there were no fields added to the search results section yet. Once I added a field in that section, the error message stopped appearing.Best Regards,James
Hi @ajayifs When possible, I think it is better practice to use an XML update instead of a direct SQL action. That way, the insert can go though a policy. It also wouldn’t require an elevated permission to execute the message.You could try something like this (replace the view name with your custom view, of course): <perform_batch> <sequential_dependent> <hierarchy_select result_name="attachmentlookup" max_rows="1"> <primary_table>c_(--some custom view--)_view</primary_table> <attrs> <attr>c_(--some custom view--)_view.attachment_id</attr> <attr>c_(--some custom view--)_view.task_id</attr> </attrs> <from> <table>c_(--some custom view--)_view</table> </from> <where> <data_constraint> <constraint> <left_operand>c_(--some custom view--)_view.task_id</left_operand> <operator>eq</operator> <right_operand>@task_i
Hi Charith, Thanks for finding that thread, it is exactly the information I was looking for!-James Byrd
Already have an account? Login
No account yet? Create an account
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.
