Not able to import/export or package the application

It sounds like you are missing something from the package and need to go back and add it and export the package again. Please provide the error details (screenshot or text) that would be helpful in resolving your issue.

Generally you should not be using packaging to export "data", e.g. Recipients or Sales Transactions. For this purpose you would use an Export job or a Data extraction (file) activity in a workflow. What type of data are you trying to export?

Linda

Thanks for your reply Linda.

We have created our application under a certain folder structure. At root we have the application folder. Then we are keeping say all delivery templates under Delivery Templates, all web forms under Web application folder etc. That is how we have organized the application.

Application folder

                Delivery Templates

                Web application

                Workflows

                Offers

We have created a package definition and added our component there. With that package, we are exporting our application. Export is successful.

But when we are importing the package, all components are getting scattered and not coming in the same folder structure we used when creating the application.

Are you exporting the folder structure including the Application folder? Have you changed the internal names on the folders, by assigning a prefix, prior to exporting them? If you can attach or e-mail me your export file, I will take a look.

I have looked at the file and there are no folders included in your export. You must export the folders as I describe here, otherwise the entities are getting placed in the default folder locations.

Hi Linda,

Thanks. You want to say that

1.  all components and the different folders, we need to give an internal name

2.  during export. when creating an package definition, we need to include explicitely the folders as well.

Please let me know if I understood correctly.

Hi Linda,

Thanks for the reply. we followed the two steps:

1.  all components and the different folders, we gave an internal name

2.  during export. when creating an package definition, we included explicitly the folders as well and for different folder we gave internal names.

but we are now facing the below issue when importing from the xml:

I have mailed the xml to you.

Please help.

Thanks & Regards,

Joydeep

Hi Joydeep,

  I looked and the entities listed are in your package. However they are probably not in the right order with regard to dependencies. So they are being referenced before they have been imported. So for example, your package imports a number of Deliveries that reference the Typology neokartTypology before you have imported it. The Typology doesn't come until later in the package. You need to be aware of these dependencies. You can reorder the entities in the package definition by moving them up and down in the list.

Linda

Thanks Linda.

We are able to solve the issue mentioned in the earlier screen shot by adding the style referenced, adding the SMS typology and including the opsecurity entry for saras.

We are able to import it now but facing two issues:

1.     Offers are not showing/coming. But in the nms:offer table we saw entry of our offers in that table.

2.. Question: we have added the campaign when creating the package def. Do we need to add each and every workflows as well comes under the campaign?

3.     In the import dialog it is showing error regarding duplicate key in workflows.

Error Log:

Submitting job to the server

17:13:07 - Enumerating the file entities...

17:13:07 - Writing entities in the database...

17:13:07 - Saving data related to packages...

17:13:07 - Package 'Neokart': Saving entities of type 'xtk:folder'...

17:13:07 - Package 'Neokart': Saving entities of type 'nms:webApp'...

17:13:08 - Package 'Neokart': Saving entities of type 'nms:delivery'...

17:13:09 - Package 'Neokart': Saving entities of type 'nms:operation'...

17:13:09 - PostgreSQL error: ERROR:  duplicate key value violates unique constraint "xtkworkflow_id"

17:13:09 - SQL statement 'INSERT INTO XtkWorkflow (iWorkflowId, sInternalName, sLabel, iModifiedById, tsLastModified, sTimezone, iFolderId, iOperationId, iCreatedById, tsCreated, iHistory, iOnError, iBuiltIn, iIsModel, iFolderProcessId, iStatus, iProduction, iState, iStartState, iPriority, mData) VALUES (:#(1)#, :#(2)#, :#(3)#, :#(4)#, :#(5)#, :#(6)#, :#(7)#, :#(8)#, :#(9)#, :#(10)#, :#(11)#, :#(12)#, :#(13)#, :#(14)#, :#(15)#, :#(16)#, :#(17)#, :#(18)#, :#(19)#, :#(20)#, :#(21)#)' could not be executed. 

17:13:09 - Param(0)=505066920 Param(1)=neokartSubscriptionWorkflow Param(2)=Subscription Workflow Param(3)=504985015   Param(4)=05/21/2015 11:43:09 AM   Param(5)= Param(6)=2926   Param(7)=505066919   Param(8)=504985015   Param(9)=05/21/2015 11:43:09 AM   Param(10)=30   Param(11)=0 Param(12)=0   Param(13)=0   Param(14)=0 Param(15)=0   Param(16)=0   Param(17)=0 Param(18)=0   Param(19)=0   Param(20)=<?xml version='1.0'?> <workflow background="xtk:backgrounds/neolane.png" modelName="opEmpty" sce

17:13:09 - nario-cs="Notification of the workflow supervisor" scenario-id="2875" schema="nms:recipient" showSQL="false" simulation="false"><activities><deliveryRecurring

17:13:09 - Package 'Neokart': Saving entities of type 'nms:typology'...

17:13:09 - Package 'Neokart': Saving entities of type 'nms:typologyRule'...

17:13:09 - Package 'Neokart': Saving entities of type 'nms:offerSpace'...

17:13:09 - Package 'Neokart': Saving entities of type 'nms:offer'...

17:13:09 - Package 'Neokart': Saving entities of type 'nms:service'...

17:13:10 - Package 'Neokart': Saving entities of type 'xtk:formRendering'...

17:13:10 - Package 'Neokart': Saving entities of type 'xtk:opsecurity'...

17:13:10 - Package 'Neokart': Saving entities of type 'xtk:specFile'...

17:13:10 - Installation of packages successful.

But we have provided unique internal names to the workflows.

Please suggest.