Loading...

Upgrading to to 6.3 qListView – Custom Display fields now cannot contain 'spaces'

Upgrading to to 6.3 qListView – Custom Display fields now cannot contain 'spaces'

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #6828
      Anonymous
      Anonymous
      Participant

      Hi John,

      n

        This change was necessary because of the new feature we added to QA 6.3

      n

      "Can add and sort custom fields to qListView/qSIListView"  (see release notes)

      n

      When you create a calculated field, there are 2 properties in ezEdit:

      n

      Field Name and Title (see the attachment). 

      n

      The property "Field Name" cannot contain spaces (ex "Full Name") but the Title can contain spaces and the Title is the value gets displayed to the users as the column name.

      n

      Please let me know if 

      n

      n

      n

    • #4661
      Anonymous
      Anonymous
      Participant

      Hello All,

      n

      If you are upgrading to 6.3 be careful. If you have any Custom Display fields [in the qListview and maybe the qSiListview as well] with ‘spaces’ in the ‘Title’  you will get a big red error! You will have to go back into the web part and edit out any spaces.

      n

    • #7330
      Anonymous
      Anonymous
      Participant

      Hi , thanks for the update. 

      n

      We [and our customers] use lots of Custom fields. It is a bit of a shock for them to do the upgrade to 6.3 only to find loads of 'RED' error messages and broken applications. Fixing the errors is not massive its more the initial shock/horror and the panic phone calls and emails from owners/users.

      n

      It is worth flagging this as pre upgrade check before jumping to 6.3 – hence my post.

      n

      Regards

      n

      n

Viewing 2 reply threads

You must be logged in to reply to this topic.