We've used the the api.Data.SetDataAttachmentText function to set the data attachments in the past. This function uses a member script to set the value in the dataattachments table which is where the annotation type data is stored. Specifically we've used this function executed from a custom calculate script to copy annontations from one scenario to another.
The attachment type is the field in this table that identifies which view member that the information is stored in; it's stored as numeric value there but the values and how they relate to the actual view members are as follows:
200 = Annotation
220 = Assumptions
221 = AuditComment
222 = Footnote
223 = VarianceExplanation
If you can generate the member script and text while in your loop - you may use this function to set the value text in the loop and the value at the end.
Yeah this is the way to go. Have you had to copy over data attachments that are actually files and not text? If yes, how did you approach it?
You know I haven't had a need to do that yet - but would be interested to hear other's ideas.
