Hello ,This error simply means that the instance you are importing the package into already has a delivery with primary key = 39594402.So there are two solutions :1>. Delete the delivery with primary key = 39594402 if it's not required in the instance the package is imported into2>. Change the conte...

Hi Salvatore,Usually the storage dimensions are same as in the OOB target mapping .You may not need to add any additional fields if not required.So I suggest , use the OOB schemas for message and tracking logs but keep the additional fields section empty.Regards,Adhiyan

Hi Salvatore,Yes this is possible by changing the target mapping.You should target the nmsAppSubscriptionRcp table directly instead of creating a Join with the recipient table.So the new mapping would look like : As opposed to the OOB Mapping of :For the second point, I think this is possible as I s...

Hi Vidya,Please perform the below steps to resolve this issue :1>. Update the allowUserPassword attribute to true in lan security zone in serverconf.xml and webservices security zone in config-instance.xml2>. add the IPv6 IP coming in the error :0:0:0:0:0:0:0:1 in both lan and webservice security zo...

Hi poorvab56881543​, PabloThis is being discussed in a support ticket , so we can mark this as resolved here.Most of the questions have already been answered.Regards,Adhiyan

Very well explained indeed Jon.We generally follow the 3rd procedure of having root+neolane in one group.davidl14970702 - When you try to connect to the sftp from a workflow , it's actually the neolane user who sends the signal to sftp and not the admin user.So even when you have admin rights you ge...

Hello Poorva,It rather looks like a warning from a typology rule 'Message Size validation ' than an error during the delivery analysis.Can you share the error log in the delivery logs.Regards,Adhiyan

Hello Richa,This message ID from the provider is stored in the table nms:providerMsgId.The part before the _1530925964 is the provider message ID.Regards,Adhiyan

Hi Rishabh,The total open and recipient open parameters are calculated for email . For push notifications the open and click implementation is done on SDK directly . So we can have only one type of Open and click for push notifications.Regards,Adhiyan

Hello Murali,It won't work if you publish the image. We had couple of issues like this before and the only way to change the image in the form template is to upload it on the server physically.You need to copy the image you are using to the directory :\datakit\xtk\eng\img\datakit\nms\eng\img or \dat...