Hi all, we are in middle of planning for complete moving data from apps to

natasav over 8 years ago

Hi all,
we are in middle of planning for complete moving data from apps to tempo interface.
We had a several discussions of what is appian best practise for doing that.
Now wee have several question about records. On the system customer wants to keep all data permanently , so we suggest to do some king of archiving or saving necessary data in SQL database and displaying those data by using tempo report and tempo records in same manner as portal reports and process instance dashboard.
So my question is it possible to set security on record data per instance or entry level in same manner as process instance security? And if it's possible how can we do it?
And on the other hand how can we display a html data by using sail?
BR,Natasa

Discussion posts and replies are publicly visible

Parents

0 Chris over 8 years ago

To expand briefly on the scalability, I ran a quick test this morning utilizing the IN operator on an entity-backed record, retrieving 50,880 records in the 'Value' (the Query Rule WAS able to retrieve that many). However, the Record works for 6-7 seconds then fails with this error in the log:

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.

That is a MSSQL limitation, assuming for which the IN operator can only be used (with poor performance) for records < 2100 potential items. Another reason we have chosen service-backed records as our primary solution.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 8 years ago

To expand briefly on the scalability, I ran a quick test this morning utilizing the IN operator on an entity-backed record, retrieving 50,880 records in the 'Value' (the Query Rule WAS able to retrieve that many). However, the Record works for 6-7 seconds then fails with this error in the log:

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.

That is a MSSQL limitation, assuming for which the IN operator can only be used (with poor performance) for records < 2100 potential items. Another reason we have chosen service-backed records as our primary solution.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data