Clarity

Hello folks, hope everyone is fine.

We are trying to XOG the project oject between two partitioned environments. More specifically, we just need to XOG 1 partition, so we used the filter `partition_code` when we requested the object in order to bring just the data of the selected partition. This is how our read XOG looks like:

One important observation about this XOG is that the create view of the project object is not being migrated. We don't know exactly why, but this would be our next question, as we want to migrate everything.

Just wondering again...

Can you split the file you are writing to sections lookups, properties and views and XOG in those in that sequence. Even more parts if you have more sections.

Secondly search the file for

&#xd

and if you find it try to figeure an aceptable replacement.

Martti K.

Thanks for your answer Martti. In fact our file had some references to '&#xd' and '&#x'. We have cleaned all this references of the file but the error persist.

We can split the file in several parts. What would be your suggestion of sequence and how can we do that?

Thanks a lot.

Vitor.

Belo are the sections which I got in an old project object read

To XOG it back in in parts I should start with the one which is the prequisite.

That is first write just the lookups.

Then the object section which has the properties and such.

Views would be the last because the has both the previous as prequisites.

If you have more sections then you would have to figure out their sequence.

If removing the character set did not remove the error, XOGing parts gives you smaller files for locating the problem.

Martti K.

Splitting the large xml file has been up a couple of times before see

https://communities.ca.com/web/ca-clarity-global-user-community/message-board/-/message_boards/message/98911244?p_p_auth=Aq0G8M5f&#p_19

https://communities.ca.com/web/ca-clarity-global-user-community/message-board/-/message_boards/message/100048879?p_p_auth=Aq0G8M5f&#p_19

Martti K.

Looking at your output from the write

Then again if you have custom attributes that have non-ascii lables those would be first thing to check.

Martti K.

Martti, thank you very much for your suggestions.

We were able to split the file in several other files and test each section to discover exactly where the error was coming from. In the end we realized that the error was in the <audit> tag. We still don't know what was the problem but as soon I have some time I will try to discover what was happening.

Regards,

Vitor.

You can split those pesky XOG files into little ones using the VisualXOG XML Splitter. 

http://www.addisonstuart.com/visualxog/downloads.html

It can split at any level in the XML, so you could take a Project XOG and Split it into Task XOGs

Give it a try!

&#xD;&#xA; are carriage returns and line feed or "\r\n"

In the Clarity UI this change of line works on Area text fields,

How can be replaced in xml (in order to keep the change of line)?

I also found problems with  a special type of double quotation mark, probably due copy paste from Ms word or web

As the normal double quotation mark  " (hexcode 22) is used by xml, when in xml content it will be translated to the  XML predefined entities &quot;

but this special double quotation marks “ ” (hexcode e2 80 9c  and e2 80 9d) will keep format and for any reason XOG doesn't like it.

Anyway at least code &#xD;&#xA; seems to be working fine in the following xml tags:

<nls description=

(/contentPack/Processes/Process/Steps/Step/Operations/Action/nls/@description)

(/contentPack/Processes/Process/nls/@description)

<Action  aiDescription="

(/contentPack/Processes/Process/Steps/Step/Operations/Action/@aiDescription)

<message description="

(/contentPack/Processes/Process/Steps/Step/Operations/Action/message/@description)

Where did you find code  &#xD;&#xA; failing?

We had experienced the error when xog-ging in the project object (with custom sub-objects) where attributes have been deactivated in the source system - and were not available in the target system.
These (inactive) attributes were setup for audit trail and have been used in NSQL-queries (and in viewFieldDescriptor).

Once we cleaned up the xml-file (removing / commenting out the deactivated attributes references) and adjusted the query the xog-in worked.

HTH.

Kind regards,

Sebastian

P.S. inactive attributes could also be activated before xog-ging out for the purpose of export, and deactivated once the export finished (to be deactivated in the target environment again); another option is to delete the attributes (with its data) prior to xogging-out.

CA PPM version 13.2