You can try this approach
First mark complete form as readonly
What you can do is create a simple rule taking input parameters for writable cells and also the row dimension and then using that populate remaining cells. Once rule is executed form renders with input and computed data.
Downside with this approach is rule has to be run multiple times based on no of row members you want to input
It cannot be done where in you want certain cells in a row to be writable first, upon inserting a value rest of the cells in that row are populated. now you want whole row to be marked as readonly. This cannot be done
Thanks for your reply - and the business rule idea is good.
So in our case the user would enter data (2-3 fields ) and then when the daily data load is complete we receive the remaining field (1) for the records with data. This row needs to be read only while the remaining as writable as it was earlier.
I believe java scripting is no more possible in 22.214.171.124 - any other suggestions?
you can try these options:
1. Split the form into multiple forms - one as data entry form where user can enter data, second which shows all the data including that was loaded or calculated
2. In case you do not want to split webforms Create a dynamic calc member which point to the member where data is loaded using the data load process. Use this dynamic calc member on the form. this will always show up as read only
Thanks for the idea - the only catch with that is - only cell would be read only at all times while the remaining would be read/write .
Just to clarify - once the user puts in data in the row ( start date /salary ..) - during the next load this data is exported to the source system and returned with certain calculations . Once that is done - the whole row would be read only .
There is a flag that denotes that the row has received data from the source system.
How about a complex form, one tab with your read only data, one with the entry, the two divided by a fix using the flag that you cite, and a context driven on save business rule which copies from flagged to flagless (or vica versa) and clears the original.
I would be weary of taking any end user reports as gospel, memory is a tricky thing and sometimes users perception is clouded by their expectation, i.e. they could have been looking at aggregated levels or similar and thinking that this was read only functionality.
True - that is a very valid point . Shall have to get proof of what they are claiming - else might be chasing my tail