[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 391
  • Last Modified:

I'm getting strange results with Three Keyword category fields that are linked (i.e. the choice in the first dictates the choices in the second, etc.)

I have been asked to carry out some quite simple modifications to the standard 'Doc Library - Notes & Web ' (doclbw7.ntf) template.

The client wishes to have three separate, but linked, levels of categorisation, which they've named File Rooms, File Cabinets & Binders.

I've redesigned the top of the 'Document' Form to display the three Keyword fields, & set up the various views for lookups etc., & it all works okay, except for one thing:

If you select a Keyword that contains a space (i.e. contains more than one word) in one field, then if you click on that same Keyword field helper again, the currently selected keyword is split at the space(s).

For example, if you select a File Room called 'Information Technology', then click on the File Room helper again, the following are listed as available File Rooms:

> Human Resources
> Information Technology
> Information
> Technology <= SELECTED KEYWORD

Of course, if you press Okay, then you reset the Keyword to 'Technology', even though that option wasn't in the list, & the option to allow keywords not in the list wasn't selected.

Is this a known issue/bug? Does anyone know of a fix or a workaround? I've discovered that if you allow more than one keyword to be selected, then it doesn't happen, but the client doesn't need to be able to categorise documents in more than one category, & because the options in the next field are dictated by the choice in the previous field, allowing multiple categories can make it look really confusing.

Thanks in advance.
0
PaulCutcliffe
Asked:
PaulCutcliffe
  • 7
  • 5
  • 3
  • +1
1 Solution
 
daj_ukCommented:
If the filed is set to allow multiple values, make sure that the properties of the field do not have the "space" set as a multi value separator

Check the Filed Properties; third table along, then Multi-Value options section

0
 
PaulCutcliffeAuthor Commented:
No it isn't set to accept multiple values, and I don't want it to be. In fact setting it to allow multiple values seems to resolve the problem, but it causes others, as if you select two categories in the first field, then you get all the subcategories from both in the second field, which doesn't really work very well & is very confusing.

I've even changed it to allow multiple values then made the separator a new line only, then set it back not to allow multiple values, but I'm afraid it doesn't make any difference.
0
 
Bill-HansonCommented:
This problem "bugged" me for years and eventually led me to virtually abandon the DialogList field type.  I've switched to using ComboBox fields in place of DialogLists.  If you don't want to use a ComboBox, you could also create your own popup control using @DbLookup and @Prompt.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
PaulCutcliffeAuthor Commented:
Bill-Handon - so do you agree that it's a bug? At least I know it's not me! Thanks.
0
 
Bill-HansonCommented:
I don't know if it's a bug or not, but I  know it's not just you.
0
 
PaulCutcliffeAuthor Commented:
Fair enough! Thanks.
0
 
qwaleteeCommented:
That's pretty odd.  Been a while since I've used a Dialog List, but I don't remember them behaving that way.  They replaced the old Keywords type field, which used to have a similar problem with commas.
0
 
PaulCutcliffeAuthor Commented:
Do you mean there were problems with commas, even if a comma was not set as a separator? If so, it could be linked.
0
 
qwaleteeCommented:
Comma was the automatic separator, you had no choice in it :(

The problem is that anything containing the separator is deemed to be two entries (if multiple entries are allowed -- otherwise, I think just one was accepted).

For some reason my dialog list now never shows the current choice highlighted when you reopen the dialog list, even if there is a single word as a choice, very odd.  I simply don't recall this behavior in the past.  I'll see if I can dig out an old app that functioned correctly.
0
 
PaulCutcliffeAuthor Commented:
Well the issue now seems to affect any Dialog List Fields that do not accept multiple values, where a single entry consisting of more than one word is selected, then the dialog box is re-opened.
0
 
Bill-HansonCommented:
If that doesn't work for you, do what I did and drop Dialog List fields altogether.  I now provide my own custom pop-ups or just use combo-boxes or list-boxes.
0
 
PaulCutcliffeAuthor Commented:
Interesting! The post you actually linked to was talking about the developer mistake of allowing multiple values, & having a space as the separator, which would of course produce the behaviour I have witnessed. However, I want my fields to be single value only, so this shouldn't apply.

However, one of the later repsonses to that thread exlained that there really is a bug that affects fields that have been switched between single & multiple value fields - which mine have been - and suggests that creating the fields again from scratch resolves the issue totally.

So that would be a solution then (again!) - thanks qwaletee!
0
 
qwaleteeCommented:
Yup, that's the one I intended to link to.

I'm not sure you have to recreate the field form scratch, you may have to just generously manipulate the sticky settings.
0
 
PaulCutcliffeAuthor Commented:
"generously manipulate the sticky settings" - love it.
0
 
qwaleteeCommented:
:)

I write documentation too. And odd error messages for events that should never occur. Of course, they sometimes do, and I then get calls asking why the computer says, "Something horrible has happened. Take three deep, slow breaths, then call support, and report error message #0y-v3y."
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 5
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now