Level 3

Solved

Error Message - ACS Publishing a Data Schema with Custom Resources

7 replies
7990 views
Translate

Hello,

This is my 1st time working in the ACS tool where I need to extend data fields on the recipients data schema.

One of the fields is a Boolean value.

However - when I got to publish the schema I get this error message.

What is this error? Is this just a warning letting me know the value is NULL since I haven't updated the field with actual data? Should I ignore this error and continue to publish?

I can't find any documentation.

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

H

holmes74338504Accepted solution

Level 3

Ramon,

So here's what I did to get it to work, I added a '_' in the name (affiliate_flag). Once I did that, the schema published and I was able to run my WF where I'm updating the fields with data from the spreadsheet.

It's so odd, because that field did not exist on the recipients table, but yet I kept getting this error.

Thanks for your help.

H

holmes74338504AuthorAccepted solution

Level 3

Ramon,

So here's what I did to get it to work, I added a '_' in the name (affiliate_flag). Once I did that, the schema published and I was able to run my WF where I'm updating the fields with data from the spreadsheet.

It's so odd, because that field did not exist on the recipients table, but yet I kept getting this error.

Thanks for your help.

Translate

B

bisswang

Employee

hm, the error looks weird.

It wants to add the column even though it already exists.

Are you already having data within this column?

If not, can you try removing it and then re-publishing the schema?

Translate

H

holmes74338504Author

Level 3

Ramon,

This is the error I get when trying to publish. Should I just continue to publish and then run a WF and update the field?

Translate

H

holmes74338504Author

Level 3

Ramon,

Here's what I'm trying to accomplish. Add this custom resource to my Profiles table. Set it as the default value.

Then in WF - load some client data from a *csv - and then perform an 'Update Data' where I will set this value to '1' for only the 200 records I will be 'inserting' to my Profiles table.

Translate

B

bisswang

Employee

Yes, that works.

Looking st the log, it rather looks like you have the field already but are planning to change the field definition?

As boolean implies NOT NULL, all data needs to contain a value.

If you have integers for now, you could try doing a small uodate workflow setting all existing records without a value to e.g. 0.

Then deployment should work

Translate