- This topic has 1 reply, 2 voices, and was last updated 6 days, 21 hours ago by
.
-
Posts
-
-
I was using the AI feature in MDFFS 2.0.10 today to configure an ideas list. I manually created the list and named it “Ideas”. I then manually changed the display name of the Title field to “Ideas”. Following that, I opened the mdffs new form configuration and used the ai to describe what I wanted my list to do. I received a prompt from mdffs which I put into my own ai, then fed the resulting json blob into the configuration page. My ai suggested a number of fields, and I didn’t notice, before approving creation of the fields, that it had suggested a DuplicateOf field [lookup]. I approved the addition of the fields, but after dffs created the fields, I got an error message that the DuplicateOf field did not exist. I tried pasting the same json blob into the AI response tab, thinking that the implementation would be idempotent. Instead, several fields were duplicated. Ask #1: Have mdffs train ai to never create a lookup field – instead, it should create a text field that can be wired up to provide the needed lookup. Ask #2: Make the implemention step, when it is creating new fields, idempotent so it will not duplicate a field that already exists on the list. To my mind, dffs should check both internal field names and display names when checking for existing fields.
-
-
- You must be logged in to reply to this topic.