Timeline for Merge field of parent template into same section of inherited template
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2020 at 17:37 | answer | added | Siva Prasath | timeline score: 0 | |
| Mar 14, 2018 at 14:00 | answer | added | Pete Navarra | timeline score: 4 | |
| S Mar 14, 2018 at 10:48 | history | suggested | Arvind Gehlot |
Removed implicit or unnecessary tag
|
|
| Mar 14, 2018 at 9:56 | review | Suggested edits | |||
| S Mar 14, 2018 at 10:48 | |||||
| S Feb 2, 2018 at 7:52 | history | suggested | Arvind Gehlot | CC BY-SA 3.0 |
Typo correction and beautification
|
| Feb 2, 2018 at 7:29 | review | Suggested edits | |||
| S Feb 2, 2018 at 7:52 | |||||
| Jan 31, 2018 at 8:47 | comment | added | Mark Cassidy♦ | Fields show up in sections named the same. So you would need to move your field to a section named the same as a section on your templates B, C and D for the field to show up there. But generally speaking, your Information Architecture is very wrong, to even end up in problems like this. | |
| Jan 31, 2018 at 6:55 | comment | added | Pete Navarra | Can you provide screen shots please? Specifically, of each template's builder, and then subsequent's base template field | |
| Jan 31, 2018 at 6:53 | history | asked | Vijaya Akkenapally | CC BY-SA 3.0 |