In our database, some fields already use the comment property for functional purposes, like this:
{"comment":"Descrição do Artigo em Português, used as a reference for other tables","placeholder":"Descrição do Artigo","tooltip":"Article description in Portuguese"}
When setting up Schema Labeling, if we also use [LLM] within the comment field, it conflicts with this existing functionality.
Is there any recommended way to bypass or work around this limitation while keeping both features functional?
Agreed, this was very poorly implemented. I use comments to store default placeholder and tooltip values (I use xml, since my ancient CFs look for that). At a minimum, Claris should have given us a closing tag to demarcate the LLM stuff. Not aware of any workaround, but in general, there’s nothing in my comments that really conflicts with what I want the LLM to know about my schema. If you’re trying to maintain valid JSON throughout the comment, you can always just include the [LLM] tag as a property inside the JSON object.
Thanks, Peter. Nice idea!
Inside the JSON, FileMaker won’t recognize the [LLM] tag, but I’ve just updated my custom function to ignore [LLM] if it exists in a field’s comment. Problem solved!