|
Dear all, We have a business process where the user locks a transaction by approving/posting it. Once the transaction is locked, no one should update or delete it but should be able to read it. However, unlocked transactions should be available for update and delete operations. One transaction may consist of one Master row and multiple detail and detail/detail tables. When locked the Master row should be blocked for Updating and Deleting and detail and detail/detail tables should be blocked for Creating, Updating and Deleting. We are able to do it in Oracle Forms simply by applying We require the same mechanism in formspider. We have checked the API_DATASOURCE manual but did not find any APIs to dynamically Insert/Update/Delete datasource at runtime. If there is any other alternatives, kindly let me know. Regards George. |
|
Hi George, The Grid has an attribute called editableColumn. This attribute points to a column in the datasource which can determine whether a particular row in the grid is editable or not. You can change the value of this column for each row in the Grid. Y sets a row as editable N sets it as not-editable. You can read more about this in this tutorial: http://theformspider.com/learningcenter/tutorial-39-how-to-use-row-cell-level-grid-attributes/ Kind Regards, |
