Maybe this is a is_html_macro that renders jinja2 with the capacity to self-reference values eg. {{FIELD_NAME}} or {{__metadata__FIELD_NAME}}. It renders in the UI read_one page ONLY, like the is_header fields. It renders at the place where it is positioned.
If render_in_create_mode is True, then you will have this rendered in the /create UI page. It will default to False. If render_in_read_mode is True, then you will have this rendered in the /read_one page. You can have both, but be mindful that the create_mode route will not have any values to reference via jinja, though perhaps via javascript pulling values from other elements...
Maybe this is a
is_html_macrothat renders jinja2 with the capacity to self-reference values eg.{{FIELD_NAME}}or{{__metadata__FIELD_NAME}}. It renders in the UI read_one page ONLY, like theis_headerfields. It renders at the place where it is positioned.If
render_in_create_modeis True, then you will have this rendered in the /create UI page. It will default to False. Ifrender_in_read_modeis True, then you will have this rendered in the /read_one page. You can have both, but be mindful that the create_mode route will not have any values to reference via jinja, though perhaps via javascript pulling values from other elements...