Trying to setup a codeless event handler. bug

Application ID: BC15B8A1-608A-D1C8-FFFE-72FC3E75A700

undefined is not iterable (cannot read property Symbol(Symbol.iterator))
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at r (
    at s (
    at Function.mapToProps (
    at r (
    at Function.r.mapToProps (
    at r (
    at Object.useMemo (
    at t.useMemo (

Problem description

Describe what you did in console that led to the error. Please provide a description of what actually happens. Be descriptive: “it doesn’t work” does not describe what the behavior actually is. This will help us with reproducing the problem.

Steps to reproduce

Please describe steps to reproduce starting from the first action.

Hi, @Will_Sargent

We are looking into it


Hello @Will_Sargent

The problem has been fixed, could you please confirm?
Did you rename ...rackMaster DataTable recently?

Regards, Vlad

Hi Vlad,

I am still getting this error (EU server BTW). Not sure if I renamed that table recently, although it’s possible.

Steps to get the problem (sorry I didn’t see this earlier on the report)

Buisiness logic
event handlers
new (also edit a problem one)
(Existing ones seem to edit ok)
model default
category data tables
event upsert (or update)
timeing before or after
context TLA_masterDatabase (although others seem to have problem)
event handler is created
click open logic designer → error

I should note that the 2-3 broken handlers I created before the bug report, which were having that behaviour, are now gone this morning after whatever fix was done.

Still having this problem.

Let me know if I can add other info.

Using Edge latest browser.

Yes, I see the error came back.
The problem was with the difference between existing tables and events handlers for that tables, I fixed the handlers manually by changing the context (TableName).
And at this moment I can see a few event handlers that refer to non-existent data tables EEL_rackMaster and TLA_masterDatabase, I believe you renamed them recently.
Yesterday we created a ticket BKNDLSS-26422 to fix the issue because there is should not be any restrictions with renaming data tables, even if they are used in event handlers.

So, in order to fix your problem need to create new handlers and move there its logic manually in files and in xml (logic) file change the root block

<block type="root_block_handler_data_after_create_EEL_rackMaster" 

to correct:

<block type="root_block_handler_data_after_create_YOUR_NEW_TABLE_NAME" 

and then deploy it from the BL → Coding screen. Or I can do it for you, just let me know new names for those tables.

I know it’s not convenient and not acceptable, I’m sorry for that, but so far the ticket is not fixed I can not recommend you better solution as `do not rename tables if they are already used in event handlers.

According to the upsert handler - this is not supported yet, it is in the testing stage.

Thanks for the update Vladimir! Makes sense. I’ll take a look at this. I am working to understand how to do full code deployments anyway… Best,

ok, in case if you have any questions or problems please let us know, we will be glad to help you