hi team, I tried to export it as package for event (Transactional
messages ) in staging env and tried to import in prod. Import went
successful however when i go to Settings >> marketing Plans >>
Transactional messages >> event configuration , I do not see the
Transactional messages that i imported. The log looks clean for package
import as shown below... Installation of packages successful.Package
'Transactional email 1': Saving entities of type
'xtk:cusResource'...Package 'Transactional email ...
We send many communication and every communcation we send we store the
values in seperate table. Unfortunatly we lost that data and now we are
trying to find out based on Campaign name or program name search the
broadlog table and find out that delivery and join with recipient and
and program table to get required value ...... is anyone did this type
of work ? Any leads , ideas please let me know.
In a workflow - I have Incremental query activity based on- @eventDate
in processed data tab. Now for temporary reason , I need full extract. I
think manually if i make last execution date of the incrementle query
activity to blank then it will automatically will run the full extract.
As my rest of the processes are set, I do not want to touch entire
workflow but i was thinking at the end of the workflow, i can add update
database field and make this "last execution date of the incremental
query...
I can see in UI that my table has only one record. This table with 2
columns become unique record. Now when I try to add another record using
create menu button on top right corner and provide both mandatory fields
it gives me error records already exists. Somehow i dont see that record
in front end in table . The actual error i am getting is :- A 'table
name' with the same key 'mandetoryfield1:mandetoryfield2' already
exists. on Clicking error details :- A 'Table name' with the same key
'mandet...
we have incremental query but requirement is for few days we would like
to have full data instead of incremental. Can i make last execution date
of the incremental query activity as null so that it can serve the
purpose ? any more innovative ideas instead of designing full query
again ?
