I'm experience a strange problem. I have a record producer which looks good. Both in the Service Portal and when I press the "try it" button on the RP. But when I look at the record created and the variable editor, it breaks some of the containers when the record is created from the Service Portal, but looks fine when I create it through the "try it".
So my thought is that inside the variables field, there must be more things than only the data which I can get through current.variables.variable_name. Here must be stuff like order etc? and I wanna compare the two record which should have the same information.... Anyone know how to do this or any other approach for this? It is also not only in one RP this happens, but it doesn't either happens to all RPs... But I haven't been able to see any same connections between the working and none working...
Here is an example of a working "variable editor".
and one that broken:
Any ideas is appreciated .
//Göran
I saw that I didn't update this topic with the solution and thought I might as well.
When a record is created like this, the variables are saved in a table called question_answer. Here you can find records like this:
As you can see I had order -100 which is a bug that happens sometimes and that leads to the strange behavior that I got.
You can read about the bug here and atm. there isn't a fix for it.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0610332
https://hi.service-now.com/kb_view.do?sysparm_article=KB0610335
My solution was to create a after BR that fixed the order by looking at the order from the record producer variables and setting it the same here.
(function executeRule(current, previous /*null when async*/) {
/*
This script is to fix the bug where SN would sometimes give variables on the record order -100 when created through
a Record Producer through the Service Portal.
*/
var qa = new GlideRecord('question_answer');
qa.addQuery('table_sys_id',current.getUniqueValue());
qa.query();
while(qa.next()){
qa.order = qa.question.order;
qa.update();
}
})(current, previous);
I saw that I didn't update this topic with the solution and thought I might as well.
When a record is created like this, the variables are saved in a table called question_answer. Here you can find records like this:
As you can see I had order -100 which is a bug that happens sometimes and that leads to the strange behavior that I got.
You can read about the bug here and atm. there isn't a fix for it.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0610332
https://hi.service-now.com/kb_view.do?sysparm_article=KB0610335
My solution was to create a after BR that fixed the order by looking at the order from the record producer variables and setting it the same here.
(function executeRule(current, previous /*null when async*/) {
/*
This script is to fix the bug where SN would sometimes give variables on the record order -100 when created through
a Record Producer through the Service Portal.
*/
var qa = new GlideRecord('question_answer');
qa.addQuery('table_sys_id',current.getUniqueValue());
qa.query();
while(qa.next()){
qa.order = qa.question.order;
qa.update();
}
})(current, previous);
