Form fails when StratusFormsData doesn't contain field for existing entry

[davidcfk]

So... you suggested to start small.

Suppose the minimalist form, you were to add a field, and the field doesn't yet exist in StratusFormsData, if you put that field in, I am getting the strange behavior that it won't allow you to save...

It's even more prominent when you do things like DDLookups, the field wouldn't even bother to load without you first manually adding that element into the key:value list...

I'm getting a list that is getting into the hundreds now so I don't fancy the idea of going in there to clobber existing entries one by one to add these fields... is there anything I am missing?

[davidcfk]

@btroop202 ? :)

[mrackley]

Sounds like a potential bug, you should be able to add fields that aren't in stratusforms data... do you mean a field to the list or a field to your HTML form?

[davidcfk]

I meant that if I have a stratus form that already has data in it, and then consequently I try to add new fields in the code only (so it then goes and adds the new fields to the stratusformsdata column only, somewhere in the code it knows an entry exists and then it fails to do two things: a) Load the form properly for new fields b) Save the new fields to the sharepoint stratusformsdata column

It may well be that (in my case), all of the fields are promoted (so really, the shortcut is simply to stick a template with blank values for all utilised fields manually into the stratusformsdata column for all entries (since it takes the values there and overrides stratusformsdata) -- but ... it isn't ideal obviously!

edit You know.. maybe it's only affecting DropDownLists that are tied with Sharepoint, have to check.

[mrackley]

Yes, check that please... The scenario you described should work fine.

[davidcfk]

Yeah. It is only when SharePoint drop down are involved it seems... Everything else works as intended.

On Mon., 1 Oct. 2018, 11:00 pm Mark Rackley, notifications@github.com wrote:

Yes, check that please... The scenario you described should work fine.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mrackley/StratusForms/issues/31#issuecomment-425898505, or mute the thread https://github.com/notifications/unsubscribe-auth/AE22I996YGhb_9AXDHa2dgNIMdF8JtqEks5ughHhgaJpZM4W908t .

[mrackley]

So, are you promoting those fields in the drop down to lookupfields?

[davidcfk]

That's correct. So, then after I got them working I proceed to add a new ddl, and the new ones would fail to work (and fail to submit) until the dummy entry in stratusformsdata was manipulated to include that value.

On Tue., 2 Oct. 2018, 12:00 am Mark Rackley, notifications@github.com wrote:

So, are you promoting those fields in the drop down to lookupfields?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mrackley/StratusForms/issues/31#issuecomment-425917768, or mute the thread https://github.com/notifications/unsubscribe-auth/AE22I0mND2_6-azIFsM9W70d6LPx0oNmks5ugh_2gaJpZM4W908t .

[btroop202]

I had the same issues, if you add a new selct list (dropdown) when you open the form there are no values in the list. I did find if you then do a save, then reopen the form you can add a value, but not 100% of the time.