xmlimport not working

Eidelman_Daniel · 2021-10-13T18:47:54+00:00

There was an error rendering this rich post.

Hi,

I've export an object (folder):

http://topentextfe20/OTCS/cs.exe?func=ll&objAction=XMLExport&objId=3641094&nodeInfo&attributeInfo&permissions

After that I try to import it with:

http://topentextfe20/OTCS/cs.exe?func=admin.xmlimport&filename=C:%5CTemp%5COTExportImport%5CexportObjID3058245.xml&objid=8527324

Then I got the status screen that say "No Errors", but when i go to the parent folder (with objID 8527324) i dont see anything that was imported.

Why cant I import

Find more posts tagged with

Comments

Hans Stoop

Is de file in the correct directory on the server topentextfe20?

For exporting you can also use func=admin.xmlexport. That has a UI to give the parameters.

I don't know how much you need to export, but if it s inot mucht, you better use the transport warehouse.

Hans

Eidelman_Daniel

Thank you for your answer. the admin.xmlexport is very handy.

I've upload the xml file from my own computer but i understant that the file must be located on the server topentextfe20? is there a specific locataion/path?
Why am I getting a positive result on an import that was not imported?
In the future we want to use automation to transter objects from Test environment to Production environment. That is why we are examine the Export/Import feature, we are thinking to use OScript for that or by the URL method. Is this the right way to transfer data? we are well familiar with the transport warehouse and use it but it is manualy and we are lookin for an automatic method. Can you please advice what is the best practice?
The Export URL has Optional Parameters, and I can see that we can export various impormation. but I can't find any parameter that export Columns and Facets with relations to the object (Folder) that is exported. is there any way to include Columns and Facets in the export xml?

Eidelman_Daniel

Thank you for your answer, the admin.xmlImport was very handy.

I've upload the xml file from my own computer but as I understant this is not the right way. the xml file must be on the server (topentextfe20)? what is the location/path?
Why am I getting a valid/success message when the actual result is false (file not found) ?
The reason we are examine Export/Import is because we want to build automation to transfer object from Test env to Prod end. I see that Export/Import can be done by URL or by OScripts. We are well familiar with transport warehouse but we use it manually. Can you please direct us what is the best practive to pransfer objects automaticly?
Columns & Facets - Is there any Optional Parameters in the Export URL method that will include columns & facets along with the XML? like we export the Permissions and the Categories. we need to link it all together (export/import).

Eidelman_Daniel

Thanks you for your answer, the admin.xmlExport was very handy.

I've upload the xml file from my own computer but as I understant this is not the right way. the xml file must be on the server (topentextfe20)? what is the location/path?
Why am I getting on the Import Status page a valid/success message when the actual result is false (file not found) ?
The reason we are examine Export/Import is because we want to build automation to transfer object from Test env to Prod end. I see that Export/Import can be done by URL or by OScripts. We are well familiar with transport warehouse but we use it manually. Can you please direct us what is the best practive to transfer objects automaticly?
Columns & Facets - Is there any Optional Parameters in the Export URL method that will include columns & facets along with the XML? like we export the Permissions and the Categories. we need to link it all together (export/import).

Hans Stoop

One limitation with XML import is that you can only create new items and not update existing items.

Another limitation is that if the export contains NodeIDs then you need to map them yourself to the NodeIDs in the target system.

The transport warehouse solves these two issues. Therefore it is better to use the transport warehouse.

The transport warehouse is also implemented in OScript so it is easy to call the actions via URL or by calling the execute function directly from OScript. Transport warehouse also support your 4th point. You just also need to transport the facets and it will automatically update the references between the folders and the facets.

Appu Nair

As @Hans_Stoop said I would ask you to use Transport Warehouse the more newer your system it is becoming a pretty decent offering . It uses xml export/ import . I configured a system in less than two hours which would have taken me days of manual work . It looks confusing but once you learn the method to the madness you will most certainly appreciate it.

Eidelman_Daniel

Thank you Hans_Stoop and Appu Nair.

So, I understand that the best practice is to use OScript with Transport Warehouse.

Hans_Stoop -

Regarding my 4th ponit, today we export manually with Transport Warehouse folders+categories+columns+facets and then import them. In most cases the import has some errors and we need manulay to fix paths to columns and categories. Furthermore we must manually connect every column to the relevant folder. Do we have those actions also in OScript?
What is the location/path that we neet to put the xml on the server (topentextfe20) with export/Import URL?

Hans Stoop

You can basically do everything in OScript and the warehouse has improved on these points. I try to do most manual changes in WebReports.

In the URL you specify the path. You should not store it inside the CS installation directory and you may be limited to the upload directory if you have configured it.

Eidelman_Daniel

Hans_Stoop, can you please give me an example/scenario on how you use WebReports insted of manual actions?

Do you have any documentation for that ?