Expand my Community achievements bar.

SOLVED

Package export error- Delivery activity

Avatar

Level 2

 

I am trying to export one workflow template in which I have a delivery activity configured with some personalized content. When I try exporting the workflow template, it is throwing the below error.

 

The 'Deliveries (delivery)' entity type uses a default ID ('DM2410') that may cause a conflict when importing the package. Change this name and repeat the operation.

I changed the delivery ID and tried, still throwing the same error.

I tried removing the delivery activity also, still throwing the same error.

 

When I created new template and copied the previous workflow template with out delivery activity and replaced it with END activity, I am able to perform the export. Now I created delivery activity and when I tried it is showing the same error.

Not sure what is going wrong, Can some help me achieving this scenario. Thanks in advance!

 

 

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Level 2

Hi @shelly-goel,

First off thanks for replying and apologies for my delayed response.

Yes, I tried exporting after changing the delivery ID and I tried deleting the Delivery itself as well yet I am seeing the same error. I thought it might be because of some caching issues. I resolved it by creating the new workflow copied from earlier by removing the delivery activities in and configured it from beginning

View solution in original post

4 Replies

Avatar

Employee Advisor

@dsomya  Yes the export would give an error with auto-created IDs for deliveries and workflows. Though if you change it to some different format, export should work fine. What is the new ID provided? Please share the package export logs.

You can try making changes to the elements in export elements and try again.

Avatar

Correct answer by
Level 2

Hi @shelly-goel,

First off thanks for replying and apologies for my delayed response.

Yes, I tried exporting after changing the delivery ID and I tried deleting the Delivery itself as well yet I am seeing the same error. I thought it might be because of some caching issues. I resolved it by creating the new workflow copied from earlier by removing the delivery activities in and configured it from beginning

Avatar

Employee Advisor
@dsomya Glad to know that you were able to resolve the issue. I've not seen any such caching issues so far, if I would change the delivery ID, atleast the error would change to reflect a new Delivery ID and not the same default ID ('DM2410'). I think we could have solved it by changing the package definition/ delivery ID though it's resolved now.

Avatar

Administrator

Hi @dsomya,

Were you able to resolve this query with the given solution or do you need more help here? Do let us know.

Thanks!



Sukrity Wadhwa