Hi Don,
In fact you can create DynamicModels with more than 30 columns. The 30-column restriction mentioned in the API Reference is a recommendation for best performance. The thing is, we have internally defined the handling of DynamicModel with 1~30 columns. If there are more columns, the product will internally use one more Dynamic model to handle the additional columns. You need not do special coding, it is just that the performance may be affected.
Note that in the 2019 GA release, you cannot use DynamicModel to generate dynamical datastore yet. We will add support of dynamically creating datastore in the coming R2 version. Please see the sample syntax that will be supported in 2019 R2 and let us know if you have further question.
//Sample 1,creating a DynamicModel datastore
string dwtext = '' ''; //assign the dw syntax to dwtext
var dataobject = DataObject.Create(dwtext);
var ds0 = new DataStore(dataobject, _context);
//Sample 2, dynamically creating a datastore model
string dwtext = '' ''; //assign the dw syntax to dwtext
var dataobject = DataObject.Create(dwtext);
var ds0 = new DataStore(dataobject, _context);
Best regards, Julie
After more discussion in house, we will remove the 30 column restriction from the document. It is not valid to put a number restriction there. As for how much will the performance be reduced by such increase, I need double check with the responsible engineer, who is currently on vacation. Please kindly wait for a few more days on this.
No... I do not think visual datawindow properties are supported.
Best regards, Julie
That is great news regarding your decision to remove the 30-column limit! Please pass along your engineer's comments on performance.
On support for datawindow visual properties, We are particularly concerned about column output formatting. Our software allows clients to create and customize what we call merge datasources. In essence, they are datawindow syntax stored in the database. Clients associate a datasource with a document that has merge fields. When the datasource is retrieved, we merge data values (with output formatting) into the document.
We plan on using DynamicModel structures to retrieve the datasource. If column formatting is not supported, can you suggest alternate methods for accessing column output formats in a .NET Datastore, whether the dataobject is exported from PB Classic or stored in a database table?
Regards,
Don Olliver
Thank you for reporting this issue. We will remove this incorrect remark (limited to 30 columns) from the API documentation, since it’s just inner detail that users don’t need to care about. You can ignore the tiny performance difference when the number of columns is increasing from 30 to 31.
For your question about column formatting, please report an enhancement requirement in the Appeon Standard Support at https://www.appeon.com/standardsupport/. It will be better if you can provide a code sample about column output formatting.
Regards,
Logan