Hi @thibaultb473199 , Does you instance has any Business Unit created?
If yes, then look for table 'business unit' and add new BU names
there.If not, then you need create one schema where you can enter names
of different 'business unit'. Also, each recipient will be associated
with one business unit, so create link between 'nms:recipient' &
'businessUnit' tables. Thanks,Jyoti
Hi @Ssb_94, error says task list you have referred in the campaign
workflow does not exist in the instance you are trying to perform
import.You need to import task list first and then the campaign.Try to
import just the task list. Make sure task list with value 'abcTSK4376,
abcTSK4378, abcTSK4387, abcTSK4385, abcTSK4382, abcTSK4377, abcTSK4379,
abcTSK4380, abcTSK4384, abcTSK4381, abcTSK4386, abcTSK4383, abcTSK4388,
abcTSK4375' exists in the instance and then perform campaign import.
Hi @Nitin_Kalra , You are getting error because incoming data does not
have targeting dimension as 'Reporting'.How have you used
enrichment?Schema coming out of enrichment should have targeting
dimension as 'Reporting'. Thanks,Jyoti
Hi @Prasanna_Soni , Are you keeping all the records since the start of
application? If no, then you must have designed some cleanup workflow to
delete recipient data after 'n' number of years.In that case, you can
design another workflow to look for primary key gaps in your recipient
table and then point out your Id to start counting for that point. Make
sure the gap is sufficient enough to add data in the table without
giving 'Primary Key Exhaustion' or 'Primary Key already exist' error.
Hi @Prasanna_Soni , Yes, you can go negative if you have not used
condition 'Primary key>0' in your workflows.Or if you are willing to do
changes in your technical workflows in order to go negative.