External custom fields: unable to change "categories are based on"

RT Users
1

Hello,

I’m trying to use external custom field values from a database of mine
and am having a weird issue where the option to select the “Categories
are based on” field is gone after selecting a Fields value source (it
just seems
to disappear).

Also, and this may be unrelated, I don’t seem to be able to change
the Fields values source field from my external values back to “Provide
list of values below”. It lets the change happen in the UI, but it
resets back
after I click “Save Changes”.

Has anyone else had issues like this?

I’m using RT 4.0.4.

-Mike

signature.asc (490 Bytes)

2

I’m trying to use external custom field values from a database of mine
and am having a weird issue where the option to select the “Categories
are based on” field is gone after selecting a Fields value source (it
just seems
to disappear).

Unfortunately, it appears that External CFs can’t have Categories at
this time (the code explicitly forbids it)

Also, and this may be unrelated, I don’t seem to be able to change
the Fields values source field from my external values back to “Provide
list of values below”. It lets the change happen in the UI, but it
resets back
after I click “Save Changes”.

I believe this to be fixed if you upgrade.
http://bestpractical.com/rt/release-notes/4.0.11

“External Custom Fields can now be changed back to internal Custom Fields in the CF Admin UI”

-kevin

3

Unfortunately, it appears that External CFs can’t have Categories at
this time (the code explicitly forbids it)

I actually failed to mention that if I select the “Categories are based
on” field and save it before switching over to the external field the ui
for creating a ticket with those custom fields behaves as expected (in
that a field that is based on another will only show those fields with
the same category that it is based on). It is as if the ability exists,
but the interface for setting it prevents that. That said, I’d
probably be playing with fire if I were to rely on it continuing to
work.

I believe this to be fixed if you upgrade.
http://bestpractical.com/rt/release-notes/4.0.11

“External Custom Fields can now be changed back to internal Custom Fields in the CF Admin UI”
I’ll check that out, thanks for the help.

-Mike

signature.asc (490 Bytes)