How to make Dictionary Overrides for scoped application

michaelsandonii · ‎09-08-2015

I have an application that I am writing, and it extends the task table. I want to change the behavior of the "assigned_to" field. In the task table, that field filters to users with the "itil" role, but I would like to use a different criteria. It seems that a dictionary override is the way to go, but dictionary overrides on task seem to be limited to the "Global" scope.

How does one get around this? Do I need a different approach, or am I missing a bigger picture?

coryseering · ‎09-08-2015

Hi Michael,

You need to add the override in your scope, on your table. I just did this on a demo instance with Fuji. First, I opened the Dictionary entry for that field, while within my scoped app:

Then I scrolled down to the Dictionary Overrides:

I clicked New and filled out my override:

I submitted the record, and verified my override was there:

That is how your override a reference qualifier on a field on Task, from within a scoped app.

View solution in original post

michaelsandonii · ‎09-08-2015

That seems to work. What's annoying is that I followed those exact same steps earlier, and the system would not allow me to select my table after clicking "New" on Dictionary Overrides. It is possible that I had already somehow switched scope, and from what I read I wouldn't be able to do so, but apparently I misstepped ... Oh well. Thanks for giving me the steps to try again and make it work. This reminds me of my early tech support days when I would show up at someone's desk and everything would be fine when I tried to follow the same steps ..

Nestor Paredes · ‎08-15-2023

Hello,

This happen on Tokyo version, a scoped dictionary override was affecting the global scope.

Had an issue with this today and after "solving" it, stumbled on this post, just wanted to share my findings in case it helps anyone else:

The table field is dependant on the Base table field, which makes sense, if you select Task as you base table, you would want that to show you "sc_task, incidents, etc".

When you are creating your override, this seems to work ok, showing you the children of your parent table.

The fun begins when you try to edit the override record. 😀

This happened after I created the record and went back to modify it...whenever I loaded the form, the Table value was blank and no value was available for pick.

The problem was that, at least in my case, it was only showing the tables inside my scope, so even if I selected "task" as the base table, the only tables available were my custom ones...leaving you with an undeletable and unmodifiable record.

I had to remove the dependency on the Base table field on the dictionary for the Table field and then I was able to change the Table value to one of my existing scoped ones and save it.

After that, I was able to delete it.

Regards,

N.