Error on split activity level with a table Account | Community
Skip to main content
thibaultb473199
Level 4
September 7, 2020
Solved

Error on split activity level with a table Account

  • September 7, 2020
  • 3 replies
  • 1387 views

Hello everyone,

I have a recurring problem on the account table "Account"
This happens especially when I load the delivery logs of the "Account" table, that I enrich and change dimension to the "Account "table. So far everything is fine but when I want to make a split using a variable of the "Account" table, I have this error message: Attribute AccountsKey1 unknow

You can see the logs of the workflow here :

This is what the workflow looks like and the issue coming from the slit activity :

What can I do a resolve this issue ? If you need more information, feel free to ask me.

Thank you in advance.

Kind regards.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by thibaultb473199

Hello,

I find the solution, this one was coming from the first enrichment that didn't have the data specified inside. Adding this one makes the workflow runs correctly.

Kind regards

3 replies

taplondon_rohan
September 8, 2020

Hi @thibaultb473199 ,

 

Would you be able to check the targeting dimension on your split activity ? Looking at the error message, it looks like the targeting dimension of your split activity and the temporary workflow table are both different (nms:recipient and thi:accounts) so the split is unable to process the AccountsKey1  attribute.  

 

 

 

In your split activity, if you set the targeting dimension to temporary schema and select the "enrichment 3" option, that should give you access to the fields from the temp workflow table. 

 

Thanks,

Rohan

 

 

Sukrity_Wadhwa
Community Manager
Community Manager
September 14, 2020

Hi @thibaultb473199,

Were you able to resolve this query with the given solution? Please let us know.

Thanks!

Sukrity Wadhwa
thibaultb473199
thibaultb473199AuthorAccepted solution
Level 4
September 17, 2020

Hello,

I find the solution, this one was coming from the first enrichment that didn't have the data specified inside. Adding this one makes the workflow runs correctly.

Kind regards