Jump to content

Dynamic Drop Down Sortby Error in Progressive Capture


Martyn Houghton
 Share

Recommended Posts

We have an existing progressive capture which has not been updated for several months, which is valid, active and operational. When I make a copy of this to test some proposed changes, but make no change at all and attempt to save/activate it reports an error referencing an issue with the Sortby function on a dynamic drop down field.

sortby.JPG

I suspect the issue has been introduced by the enhancement for the sort order on dynamic drop down list using simple lists as the source. I have quite a lot of custom forms in the PC, so is it a matter of just opening up each node to refresh it or do I need to go into each dynamic drop down field to set/reset a sort order to resolve this issue?

When I go into a field the sort order is displayed, but I presume this is just defaulting in the UI and the underlying value prior to going into the form is empty so the PC will not pass validation until it is populated.

Cheers

Martyn

 

 

 

Link to comment
Share on other sites

Hi Martyn,

We have identified the issue, but looks like it will need a core fix. So in the meantime i am removing the sort by and order by properties for the dynamic lists. Will see if we can get it out today.

Cheers

Link to comment
Share on other sites

@Lyonel

I think this might be a different issue. That error normally indicates that you have  invalid characters, mine where always spaces, in the form id of one of your custom forms.

It could be with the changes to the Admin Tool, that the validation criteria has changed in someway, which is why the error disappeared and then came back.

Cheers

Martyn

Link to comment
Share on other sites

Hi Lyonel,

We fixed and pushed out the Save and Validate issue with the sort by param yesterday lunch time, so that will be why that works ok now.

As Martyn says the formId issue will be due to spaces or other special chars in the formId. This should just contain aplha numeric chars and underscores. It should not start with a number.

Unfortunately our serverside validation doesn't pump out useful error messages. I will add a client side validation check.

Cheers

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...