Congrats @_Manoj_Kumar_ 

Share the whole script.

Hey  @_Manoj_Kumar_    If you check the update the preloaded record, it will disable the checkboxes below, and update everything, if I Uncheck it then those fields that are selected are used to reconcile to existing recipients.   For instance, in my case, if I select First Name Last Name and Email, ...

I would set a constraint on the database level to make the email field mandatory on what ever schema is being left empty. alter table xxx alter column columnxxx varchar not null; Furthermore, I think you can configure the loading activity to make certain fields/columns mandatory (non empty) and ther...

On webapps, the storage activity does not allow you to exclude fields, by default it just updates all data submitted from the front end forms, the way to get around this is to use javascript on both front end (to assign field data to variables) then on back end to manually handle updating the fields...

Try the below;   <% var ctx = XML(rtEvent.ctx); % > <% if (rtEvent.ctx.@freeText22 == true) {% > <tr> <td class = "mpbx-27" style = "font-size:16px; line-height:22px; font-family:'Core Sans C', Helvetica, Arial, sans-serif; font-weight: 400; text-align:left; min-width:auto !important; color:#151...

Is that multiple servers connected to the same DB (with failover/idle box?)   Could it be a previleges issue? try logging with the internal account Are your services configured correctly in the in conf backend files? Was it a DB restore from other environment? or fresh db deployment Whats the DB typ...

I don't think we have that in ACC, unless you manually extend the recipient schema and start passing your recipient's timezone to ACC and have a marketing campaign take that into consideration. (or look into Adobe Sensei)   <attribute default="'_server_'" desc="Recipient time zone" name="rcpTimeZone...

Would be nice if you could attach the full content of the personalization block.

Hey Marcel, Can you check if you have any form conflicts as a result of a recent upgrade, if you do, accept the latest version and merge any customizations.   Please see attached more details on the NEO-48807 bug.   The “query is too complex" issues encountered were due to multiple factors occurring...