Decision Table does not do the matching for the reference field

mfhaciahmetoglu
Mega Sage

Hello,

 

I am creating a decision table for the delivery location. Based on the "Delivery Location" field (reference to cmn_locations table), I do the matching on the decision table and assign the tasks on the flow to specific groups.

 

It is simple but for some reason, it does not work. I tried to two ways.

 

1. I create the decision action and dot walk to delivery location (reference to cmn_location table) to Name field. 

mfhaciahmetoglu_0-1709904964358.png

 

2. I see that the input is correct here: NOI. However notice that, it says record is not found. Weird.

mfhaciahmetoglu_2-1709905131095.png

 

3. Then on the Decision table, I tried both string input and reference to Location.Name

 

Here is the string input:

mfhaciahmetoglu_3-1709905207130.png

 

 --> So it should assign it to IT AMER but it does not do the matching and the ticket goes to default result. 

 

Anyone has any idea why?

 

Another weird point is that when I choose input Reference to cmn_locations table and dot walk to location.Name, the select box does not automatically show me the name field. It remains to be a string.

 

mfhaciahmetoglu_5-1709905937134.png

 

 

 

 

5 REPLIES 5

mfhaciahmetoglu
Mega Sage

Hi again,

 

I found a workaround by creating a string flow variable and assigning to it the deliver_location.Name. 

However, still I don't understand why these features do not work properly.

 

Best,

Firat

Hello, 

Would you mind sharing your workaround that you came up with? I have a similar issue and haven't been able to get it to work properly either. 

Thank you, 

Josh

Would you please share the workaround. I am getting similar issue:

getGlideElement called for unknown field 'country' in table 'var__m_sys_decision_input_<sys_id>

 

Hi, my solution was the following:

1. Use string input on Decision Table.

2. In the flow designer, create a string flow variable and assign the reference to this variable. 

3. Push this flow variable as input to the decision table.

 

Unfortunately, this means that you need to build the decisions manually one by one on decision table but there is no other solution possible at the moment. 

 

Best,

Firat