Hi Jolyon,
We are sorry that you encountered this problem. We reproduced the described exception, if any of the following conditions are met:
1.Custom fields are added to an aggregate storage before adding custom fields to linked storages.
2.The number of custom fields differs in an aggregate storage and linked storages.
To overcome the problem, make sure that:
- Custom fields are created first in linked storages, and then in an aggregate storage. Also, we recommend that you enclose the code adding custom fields into an aggregate storage in BeginUpdate/EndUpdate method calls.
- The CustomFields collections contain the same number of custom fields before new fields are added.
Due to these finding, we've converted this question to a bug report. Our developers are already searching for a solution to this issue. Please stay tuned for updates.
Thanks,
Alex
Is your intention to post an answer to your own question?
- If so, then proceed.
- If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
- If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.
Facebook
Twitter
Google+