Forum Discussion
Apparently not...
I may have a suggestion but am not sure I fully understand your situation. Is this what you are trying to do?:
- An EOTI user accesses a Parent record using the new form view
- They need to create a child record from that parent/form via an embedded report
- They should NOT be able to edit any existing children from that report
Do I understand it correctly?
- MarkShnier__You2 months ago
Qrew Legend
My suggestion is to make a super mini Legacy Style form with a couple of identifying fields at the top and an Embedded Child report which is set to be editable.
Then make a simple formula URL button to put the record into Edit mode using that form. Then you will get the Legacy Form Experience.
URLRoot() & "db/" & Dbid() & "?a=er&dfid=11&rid=" & [Record ID#]
// 11 is the Legacy form style mini form ID.
- ChristopherWhea2 months agoQrew Cadet
Thanks, Mark. The challenge here is that they need to do everything in one go...as soon as they navigate away from the page the submission is gone.
- ChristopherWhea2 months agoQrew Cadet
Hi Aaron,
The use case is that EOTI can click a link on a public-facing website that will allow them to create a new record on a table. It's similar to the long-standing solution of allowing contacts to update their information without a login using the GenAddRecord API (Kirk Trachy's, maybe?). So they cannot View or Edit any records. Everything has to happen in one shot because as soon as they navigate away from the page the record is saved ("submitted").