Timeline for Changing FormField ControlMode from code-behind causes strange behaviour
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20, 2017 at 13:20 | answer | added | Mariusz Ignatowicz | timeline score: 0 | |
| May 9, 2017 at 9:20 | comment | added | Danny '365CSI' Engelman | That's why Microsoft came up with CSR .. And yes I wouldn't be surprised if they tried a single-form as well.. and then they learned they shouldn't mess with SP2001 code. Take into account CSR is no longer there in SPOnline Modern Experiences (SPFx).. but neither is that SP2001 code. SharePoint finally is becoming a modern SPA... But the essence is the same as CSR, no more back-end code, it's the Client that requests content. So CSR code you develop now, should easily be ported to SPFx (it's all JavaScript). Use Cisar for CSR development | |
| May 9, 2017 at 9:17 | comment | added | Mariusz Ignatowicz | @Danny'365CSI'Engelman Because if there is a requirement to change something on the form (for example order of the fields) I change it in 1 place instead of 3 places. | |
| May 9, 2017 at 9:13 | comment | added | Danny '365CSI' Engelman | Question: Why do you want one page? To the user there is no UX difference, other then the URL. You are now working against the grain, and having to pay for it. If there was an advantage in a single-Form; Microsoft would have refacterod their SP2001 approach a long time ago | |
| May 9, 2017 at 8:49 | history | asked | Mariusz Ignatowicz | CC BY-SA 3.0 |