Merging Attributes on Word Export

llandale - Tue Mar 19 14:24:30 EDT 2013
Add double-double quotes to force reading the attr-value.

• (o."Attribute 1" ""> "XYZ.")

• o."Attribute 1"

• string s = o."Attribute 1"

• o."Attribute 1" ""

SystemAdmin - Tue Mar 19 15:44:38 EDT 2013

Ok, that helped but now I still have a problem with the wordDumpObjectVBA. Unless I misunderstood some of the previous information you provided. Here is the new error and the updated modified code per the previous comments.

Error:
-E- DXL: <Line:2670> incorrect arguments for function (wordDumpObjectVBA)
-I- DXL: All done. Errors reported: 1. Warnings reported: 0.

if (o."Attribute 1" ""> "XYZ."){    // **** User Mod Start ****
                string temp = o."Attribute 1" ""  " " o."Object Text" ""
                wordDumpObjectVBA(temp)
                exportStepProgress
                }
                else { // **** Mod End ****
                wordDumpObjectVBA(o)
                exportStepProgress
                } // **** remove this bracket if this dosnet work. ****

Again thanks in advance for the input, it is very much appreciated.

SystemAdmin - Tue Mar 19 16:36:31 EDT 2013

The declaration for the wordDumpObjectVBA function is

void wordDumpObjectVBA(Object o)

The 3rd line in your code snippet is trying to pass a variable of type string to this function when it expects a variable of type object.

The location where you need to concatenate two object attributes into a single string needs to be done inside the wordDumpObjectVBA function. However, this function is loaded with a number of exception checks and also works on whatever columns are present in the current view. So I wonder if it would be easier for you to have a DXL Attribute column in a view that concatenates the two attributes of interest so that you don't need to modify this code?

Paul Miller,
Melbourne, Australia

SystemAdmin - Wed Mar 20 09:44:23 EDT 2013
Your suggestion above has been tried already. The results of that were a lot of extra cleanup work after the export. As the export file needs to be in the book style. I am trying to avoid that, if there is another method to export the concatenated items I am open to try that suggestion. Again thanks for your response, it is appreciated.

adevicq - Wed Mar 20 09:57:44 EDT 2013

Hi,
You can use the following function:
 

string applyStyleLockPasteInvokeBuf(OleAutoObj objSelection,
                                 Buffer s,
                                 string styleName)

You can build your string and export it to the word doc with a specific style (null if you must use the normal style).
This method is included in the standard word export.
Regards,
Alain

SystemAdmin - Wed Mar 20 11:23:09 EDT 2013

I gave this a shot but, again I am either misunderstanding or this is not working properly. The code runs but I am only getting the items that don't have "Attribute 1" populated. So If I have ten objects in my module and seven of them have "Attribute 1" populated only three objects are getting exported. I am not sure the function "applyStyleLockPasteInvokeBuf" works the way I want. The fact that it is only exporting some of the objects means to me that the "If" statement is working correctly. It is just the export part of the combined items that is not getting exported.
 

if (o."Attributee 1" "" > "XYZ."){    // **** User Mod Start ****
        Buffer temp = create
        temp = o."Attribute 1" "" " " o."Object Text" ""
        string applyStyleLockPasteInvokeBuf(OleAutoObj objSelection,
                        Buffer temp,
                        string styleName)
        exportStepProgress
}
else { // **** Mod End ****
wordDumpObjectVBA(o)
exportStepProgress
} // **** remove this bracket if this doesn't work. ****

adevicq - Wed Mar 20 13:10:45 EDT 2013
Hi,
The method exports what you tell it to export.
You probably do not enter the piece of code.
Print something before the call to applyStyleLockPasteInvokeBuf. I'm pretty sure that you will discover that your condition is not correct...
Alain

SystemAdmin - Wed Mar 20 14:28:38 EDT 2013
Again I did as you suggested the exported word file only contains items that don’t have “Attribute 1” filled out. While the print showed me exactly what I wanted. Now I know for sure the problem is with the “applyStyleLockPasteInvokeBuf”. As the print showed the following:

XYZ.XXX Object Text Sentence
XYZ.XXX Object Text Sentence
XYZ.XXX Object Text Sentence
XYZ.XXX Object Text Sentence
XYZ.XXX Object Text Sentence
XYZ.XXX Object Text Sentence

This happened for all the items that have “Attribute 1” filled in. to me this proves my “IF” statement is working properly the method to export the information to the word file is not right.

SystemAdmin - Wed Mar 20 17:14:50 EDT 2013
The "IF" statement in the code snippet of your most recent post seems to have a typo error - the word "Attribute" has two e's on the end of it - i.e. Attributee. But that should have raised a DXL "unknown Object attribute" error as opposed to the condition never being true.

You said that my earlier suggestion to use an Attribute DXL had been tried but required post export formatting of some sort. Does that you mean you tried to export in Book format and you still had to do soem clean up, or you thought that you had to use Table style to do such an export?

The Book style export works to whatever is the currently visible View in the DOORS module. If you insert a column where a DXL Attribute has performed the concatenation for you, then that DXL Attribute column and all other visible columns in the VIew should export in Book style as required.