Workspace Reference field shows Sys IDs instead of the Display Value

Jay D1
Tera Guru

Hello,

I have a reference field with a reference qualifier (javascript:new ScriptInclude().myFuncMatrix();) looking at a Script Include. On the UI Form, I am getting the correct display values while on the workspace, I get the Sys IDs (Screenshot below).

find_real_file.png

myFuncMatrix: function() {
		var letterList = '';

		var choiceSysID = new GlideRecord('sys_choice');
		choiceSysID.addEncodedQuery('element=subcategory^name=table_name_A^dependent_value=4^value=' + current.subcategory);
		choiceSysID.query();

		while(choiceSysID.next()){

			var gr = new GlideRecord('table_name_B');
			gr.addEncodedQuery('table_name_B_subcategoryLIKE' + choiceSysID.getUniqueValue());
			gr.query();

			while(gr.next()) {
				if (myFunc.length > 0) {
					myFunc+= (',' + gr.sys_id).toString();
				} else {
					myFunc = gr.sys_id.toString();
				}
			}
			return 'sys_idIN' + letterList;
		}
	},
1 ACCEPTED SOLUTION

Hi,

I tested this before I replied, I don't usually just reply with random things on the forums here, but when I adjusted the popup view in the standard UI, it was reflected upon reload within the Workspace.

Example:

I navigate to an Incident record in standard UI, click the magnifying glass for "Caller" field to see popup view:

find_real_file.png

I navigate to Agent Workspace, Incident record, Caller field, popup is:

find_real_file.png

I go back to Incident, standard UI, remove the email field from Caller popup:

find_real_file.png

Go back to Agent Workspace, refresh, click Caller reference again:

find_real_file.png

So, anyways, it's controlled from the same place. Normally, when you first create a brand new table, and you go to access a reference field that points to it, it shows just the sys_id column initially.

Once you create the popup view, it shows what you've set.

I don't know if this is a custom table that's being pointed to or maybe you had a table defined, but then removed it, and so the Workspace UI is not picking that up. Since you're using a reference field is a different way, by adding choices to it, instead of it pointing to a table, there may be some issues there.

You can temporarily add a table back to the reference field, then check Standard and Workspace UIs and see if they align.

Then, swap back and remove that table reference, and see if that resolves anything. You can also try clearing your instance cache by typing: cache.do and pressing enter in left-hand navigation.

You can check the URL in the popup in standard UI and see what table it's pointing to, is that correct?

The Workspace UI may be pointing to a different table and so it's not the same table, thus the popup view is different. Workspace could be looking at sys_choice, whereas your standard UI may be looking at a different table?

Please mark reply as Helpful/Correct, if applicable. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

View solution in original post

9 REPLIES 9

That is a good point, though how would you update the columns on a workspace popup?

Hi,

They should pull from the same layout.

So in your standard UI, if you navigate to that same reference field, open it up (click magnifying glass, etc.), right-click any column header in that pop-up and verify your layout, the same will be shown on the workspace.

I'd recommend doing that and just double-check that you've actually set a layout for that popup.

Please mark reply as Helpful/Correct, if applicable. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

That is certainly helpful but the list view on the Standard UI is correct while the Workspace shows Sys ID. Making me wonder if there is a different place for Workspace!

Hi,

I tested this before I replied, I don't usually just reply with random things on the forums here, but when I adjusted the popup view in the standard UI, it was reflected upon reload within the Workspace.

Example:

I navigate to an Incident record in standard UI, click the magnifying glass for "Caller" field to see popup view:

find_real_file.png

I navigate to Agent Workspace, Incident record, Caller field, popup is:

find_real_file.png

I go back to Incident, standard UI, remove the email field from Caller popup:

find_real_file.png

Go back to Agent Workspace, refresh, click Caller reference again:

find_real_file.png

So, anyways, it's controlled from the same place. Normally, when you first create a brand new table, and you go to access a reference field that points to it, it shows just the sys_id column initially.

Once you create the popup view, it shows what you've set.

I don't know if this is a custom table that's being pointed to or maybe you had a table defined, but then removed it, and so the Workspace UI is not picking that up. Since you're using a reference field is a different way, by adding choices to it, instead of it pointing to a table, there may be some issues there.

You can temporarily add a table back to the reference field, then check Standard and Workspace UIs and see if they align.

Then, swap back and remove that table reference, and see if that resolves anything. You can also try clearing your instance cache by typing: cache.do and pressing enter in left-hand navigation.

You can check the URL in the popup in standard UI and see what table it's pointing to, is that correct?

The Workspace UI may be pointing to a different table and so it's not the same table, thus the popup view is different. Workspace could be looking at sys_choice, whereas your standard UI may be looking at a different table?

Please mark reply as Helpful/Correct, if applicable. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Thanks for all the knowledge Allen. You are correct, the popup view would be the same. But that didn't take effect immediately but worked on the following day. I suspect cache was the cause on why it didn't reflect the change immediately. I remember doing cache.do the prior day but for some odd reason, this change didn't take effect until the next day!!