Heads up on List control - may not return Primary Key after edit in v4

[peteconway]

Just letting you guys know that I have noticed - some of my pre v4 lists fail to return the primary key after editing a UX and saving, if you bump into the issue I have found the only way to get around it is to rebuild the list. - Maybe a glitch in my system - but this note may save you lost hours if you experience it. First sign something is wrong is the submit fails. - i'll let alpha know.

Cheers Pete


Update on this - have not seen the issue in the last few hours - so i'm not getting bent out of shape on this, so just ignore the post.

Pete

[txsiccness]

Re: Heads up on List control - may not return Primary Key after edit in v4

You say "some of your pre v4 lists fail to return the primary key", have you noticed any other pre v4 lists that do return the primary key?

[iRadiate]

Re: Heads up on List control - may not return Primary Key after edit in v4

Just letting you guys know that I have noticed - some of my pre v4 lists fail to return the primary key after editing a UX and saving, if you bump into the issue I have found the only way to get around it is to rebuild the list. - Maybe a glitch in my system - but this note may save you lost hours if you experience it. First sign something is wrong is the submit fails. - i'll let alpha know.

Cheers Pete

I haven't run into this yet with any of my pre v4 lists, but thanks for the heads up.

[CharlesParker]

Re: Heads up on List control - may not return Primary Key after edit in v4

I think it depends on filter settings using session variables, if your using them. I had a char value as a filter but the update is requiring that it be numeric. Turns out I had set a field to a char value in a list controls detail view that was supposed to have been a numeric value. This caused problems however, Alpha's code actually caught it for me and I soon discovered my error - not theirs so in the end I fixed my fields type and re-created the variable. Now it works again. I am not sure if this would be the issue for you guys but for me all I saw was a list that worked before I updated and then one that no longer worked.
Of course, I thought well there's a bug - but as usual it was me...lol.
Another issue I came across after updating to the last release was that my lists were no longer showing the way they used to but again, I had no code in the list to define placement. Now that works very well, and again in the end it was me who was doing some sloppy work.
One thing I know is if there's a bug, they find it and squash it.

[peteconway]

Re: Heads up on List control - may not return Primary Key after edit in v4

Riley - Yes.

[peteconway]

Re: Heads up on List control - may not return Primary Key after edit in v4

Update on this - have not seen the issue in the last few hours - so i'm not getting bent out of shape on this, so just ignore the post.

Pete

[istuart]

Re: Heads up on List control - may not return Primary Key after edit in v4

I've never had an issue with the list primary, however, I don't usually use the configured primary key inside of the list control. Instead, I like to hide a text field somewhere on the page and set the value of the primary key there using an onClick action javascript from the list properties. This comes in handy when you need to populate other controls (not just a child list) or set argument values, local filter values, or to trigger another action with an onChange event.

Another thing I like to do is set the filter of a child list on the argument value of the hidden pkey text field instead of setting up the parent-child relationship of two or more lists. If the lists are set up that way, you are not required to refresh the top-most parent when attempting to refresh a child list.