I recently started using relational picklists with the following hierarchy:

    Application

        Component

         Version

When adding these fields to my template, the seem to work properly for creating a defect.  However, when I go back into a defect that I had originally saved, the field values for the children are not showing up.  So, the Application field is still filled in fine but Component and Version are empty.  BUT I don't think that they are really empty because I can see them in my main window if I select those fields as columns and I can see them when I 'view' a defect in the Web Client.  If I go into 'Edit' the defect in Web or Windows, they are gone???

I am logged in as the same user in both Windows and Web client.  I have logged out and back in with same results.

Running version 7.1.2.7389.  Just upgraded to it last week.  I was not using relational picklists prior to that time.

One other note, it does not do this for every template that I have set up.  For some, this is not an issue.  It does seem that it is happening on Templates that existed prior to the upgrade, but with newer Templates, they work OK.

I am demo'ing this for some decision makers today (on purchasing this product) and was making some final touches to my preparations when I discovered this.  They will not be pleased to see this is not working.

Hello rschoessler,

I can imagine how those decision makers would not be pleased. Yet, hopefully you'll all be pleased to know that there is a logical reason for what you're seeing, and with a few simple changes you can resolve it quickly and easily. 

The reason your child picklists aren't displaying the data correctly from the 'Edit' windows is because of the order you've placed those picklists in the Field Template.

You mentioned that this only occurs with certain Field Templates, so that would be the first place for us to make a few changes. Edit one of the templates that's experiencing this issue by going to "Tools>Manage Field Templates". Once you've opened your template and you see all your fields listed, notice the order of your 3 dependent picklists from top to bottom. The order in which the OnTime 'Edit ' window displays the data for each field is from top to bottom. So, if your children picklists (Component, Version) have been moved up above the parent picklist (Application), then that dependent data wouldn't have been determined yet to display in the 'Edit' window. The data exists and is saved correctly in your database, as you can see from the main grid.

All you have to do is rearrange the order of those picklists so that any parent picklist is listed above any children picklists on that template. Save the template, edit the item again, and the child picklist values should display correctly.

There's one other place this same principle comes into play. If you adjust your templates and the issue still seems to be occuring, you'll need to check your list of Custom Fields. Go to "Defects>Manage Custom Fields" to see the listing of all your custom fields for defects. Just like with templates, you'll have to make sure that the parent picklists are listed above the children picklists. Rearrange the fields if needed, and check your Edit windows again.

That should resolve your issue, and hopefully please the decision makers who will be considering purchasing OnTime.

Let me know if you have any further questions prior to your demo.

Rearranging the order in the template has corrected the issue.

I would think that the order wouldn't matter but I'm assuming that it is a design issue of some sort.

Thanks for taking the time to explain the issue.