List detail error when clicking on list row

[CharlesParker]

Re: List detail error when clicking on list row

Yes, but again this would assume a NEW RECORD only - default value does not run on an existing record, only a calculated value would unless I am mistaken.

[Peter.Greulich]

Re: List detail error when clicking on list row

I believe if you use the default value property of the control it sets the flag dirty

You might be on to something. Thanks for the tip.

[CharlesParker]

Re: List detail error when clicking on list row

so how is the UX called?

[frankbicknell]

Re: List detail error when clicking on list row

Something is setting the list dirty flag. It might be the default values. Where are you setting them? I believe if you use the default value property of the control it sets the flag dirty. You may have to use the Default value Javascript in the Detail view properties of the lists fields tab.

[Peter.Greulich]

Re: List detail error when clicking on list row

Why not create a new UX and try to duplicate the issue, perhaps it is version specific.

It may be version specific. Or it may be something "wonky". I can't post the client app. But I'm hoping to have someone else look at it.

Thanks Charles.

[CharlesParker]

Re: List detail error when clicking on list row

as far as I know clicking on a row cannot add a new record unless you tell it to, how do you "go to the list"? I re-read your post a few times it should work with suppress global error alerts and auto -commit.
Even if the list has default values, that doesn't set the list to dirty, client-side calculated values do not either or we wouldn't have to to use e.dirty.columns in dialogValidate. This would drive me nuts.
Is Only validate values that were changed ticked in the properties of the UX?
Keep in mind - I am simply looking at my UX's that work as expected and going over things that I know or seem to make things happen for me. I am in no way telling you like I am some sorta expert, lol BUT somethign is wonky there because it shoudl be working and I know you've been around long enough to know too.
Why not create a new UX and try to duplicate the issue, perhaps it is version specific.

If nothing else you coudl post the UX but again being that it's an older version someone with that version to test in would have to do it to rule out a version specific caveat - but I still think it's somethign in the way the list is loading because I don't see how clicking a row can add a record instead of update the existing one.

[Peter.Greulich]

Re: List detail error when clicking on list row

It seems like you are programmatically changing the value of one of the controls in the detail view. Do you have default values set for some controls?

Frank,

Yes, I have defaults set in a bunch of controls.

[frankbicknell]

Re: List detail error when clicking on list row

It seems like you are programmatically changing the value of one of the controls in the detail view. Do you have default values set for some controls?

[CharlesParker]

Re: List detail error when clicking on list row

Also - check "suppress global error alerts" unless you want users to see them

[CharlesParker]

Re: List detail error when clicking on list row

oh, congrats on your expecting UX, lol - if I were you though I would adopt and create a stand alone UX and call the related record with arguments instead of using parent-child setup. I think it loads faster (without pagination of course) because your loading each record and each associated child record - this for me has always equaled slow load times of data eventually as users stack up.
back to your original issue though, you need to look at the allow a NULL selection or not to first. I say this because if you do not allow a null selection the first thing that is going to happen is your going to have the first record selected - now this is where it might get tricky. I think if it's a new list with no records, it might actually create one setting it dirty and causing your issue right there - now I am not sure about an empty list so take that with a grain of salt. Regardless you might not want the list to load with a record selected, but if there are child records you might want that behavior - so again it's apoint to ponder. I prefer to allow a NULL selection myself and let the user choose what they want to select. Then I check the auto-commit on row select and set the syncronization policy to client to server.


I

[Peter.Greulich]

Re: List detail error when clicking on list row

It's a standalone list at the moment, soon to become a parent.

[CharlesParker]

Re: List detail error when clicking on list row

Is this a UX with a single list or is this a child list? I have run into this before with parent child list associations.

[Peter.Greulich]

Re: List detail error when clicking on list row

That didn't fix it.

It has something to do with the "auto-commit view on row select'. If it is not checked I get the above error. If I remove the error message as shown above I can't select the row. Checking the box gets rid of the error message and allows me to select a row. BUT, whenever I logout and log back in and go to the list and click on any row, it ADDs a new record to the list. This is really really frustrating. Only happens on a brand new login.

Auto-commit error.png

[Peter.Greulich]

Re: List detail error when clicking on list row

Fixed!

I slayed the monster (this only took 4-5 hours to figure out).

Set the dirty field warning customization to blank. No more popups.

See image...
Dirty row error fix.png

[Peter.Greulich]

Re: List detail error when clicking on list row

What happens when you set it to read only in the properties?

Same thing. Still get the error.