Hi!

I'm working on a data export function from our software into Word2k7, using
CustomXMLParts therefore to save the Data to docx and a COM-AddIn to step
through the single DataSets.

Everything worked pretty fine until i updated to the Technical Refresh.

Now i can't get the CustomXMLParts out of the docx anymore.
I checked the unzipped docx files and they are alright - they got the
correct GUID, but when i call for (from the Add-In):
Office.CustomXMLPart customXML = _Doc.CustomXMLParts.SelectByID(MYGUID);
it returns null - but that's just since the technical refresh!

Did they change anything concerning this? I've already read thousands of
blogs (or maybe a few dozens ;)) but I haven't found anything helpfull ...
hope somebody can help me - i really got stuck on this

thx in advance!

also postet this on: http://www.microsoft.com/office/community/en-us/default.mspx?dg=microsoft.public.word.vba.general&lang=en&cr=US

Hi Johnny

Yes, the file formats have changed (again); MS even warns that entire files created in earlier betas may not be accessible in the B2TR. You should find some information at pschmid.net, including a list of some of the possible results of the change. I'm not sure whether Patrick also has your problem listed, but it definitely could be a result of the file format change.

hmmm ... thx, but i don't think it's a problem of file format changing ... because i fill the docx with the custom xml programatically also in the b2tr - and when i start XML Data Store Explorer in Word i can see all added Data correctly and when i open the file ..\customXml\itemProps1.xml it has its entry:
<ds:datastoreItem ds:itemID="MYGUID" xmlns:ds="http://schemas.openxmlformats.org/officedocument/2006/2/customXml">
<ds:schemaRefs><ds:schemaRef ds:uri="http://schemas.mycompany.com/2006/customTags"/></ds:schemaRefs></ds:datastoreItem>

so, the guid is assigned correctly too, but out of the Add-In i only get a NULL-Value when i call:
Office.CustomXMLPart customXML = _Doc.CustomXMLParts.SelectByID(MYGUID);
i really get desperated about this, cause i need it urgent...

thx anyway

Hi Johnny

Hmmm, might be looking at a bug. But we'd need more detail on exactly how you're setting this up (repro steps) to test/confirm.

Well, thats very complex how i'm generating/injecting the Custom XML into docx, but in most simple words:
well, I generate all needed files/folders on my own programatically (customXML/item1-3.xml;itemProps1-3.xml;/_rels/item1-3.xml.rels)
when i set up the connection for the dataset it's guid is set to my special guid; then i add my columns and rows needed (most likely stuff like: firstname, surname, ...)
this happens when the word-file is opened out of our program and hasn't yet any custom xml.

then i got 2 COM Add-Ins - 1 has just a DocumenentOpenEventHandler and activates the second, which should insert Content Controls, but i need to check, if the file has my CustomXML which is needed for the Content Controls of course ... so i call:
Office.CustomXMLPart customXML = _Doc.CustomXMLParts.SelectByID(MYGUID);
and here is where i get my NULL value ...
maybe i could send you a docx-file with my CustomXML injected, so you could try a bit with it ...

but I'm NOT using the new windows SDK - and i MUST NOT use it ...

thx for your quick answer

The namespace of the custom XML data properties part you're writing is from Beta2, and so Word doesn't load it. If you remove the /2/ from the namespace, it should work, since then it's the correct final namespace.

Tristan

well, thx - that's a good hint, but it still doesn't work ..

what i've found out now is:
xmlWriter.WriteLine(@"<ds:datastoreItem ds:itemID=""" + _Con.Guid +@""" xmlns:ds=""http://schemas.openxmlformats.org/officedocument/2006/customXml"">");

simple doesn't write the correct ID into the itemPropsX.xml file ..

somehow the itemID is getting changed to some newly generated one and that's why i can't get my CustomXMLParts by ID of course ...

well, i'm already working a few days on this problem but i can't manage it to work properly - i've achieved to actually get my CustomXMLParts, but in a unsecure, unclean way :)

anyone else experienced that problem as well??