We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FRSL is not working in the Record Status Dashboard when Dynamic Data Pull (DDP) is enabled.
When DDP is enabled, it modifies the record table by adding an extra column as shown in the figure bellow.
This extra column appends one extra <a> element per row:
<a>
The FRSL fails when Record Status Dashboard is opening. The following message is shown in the browser console:
This error is thrown when FRSL tries to process the <a> element that comes from the DDP code.
After this error, the JS code stops and the module does not work as expected.
I coded a workaround for this problem that just ignores the <a> element that comes from DDP stuff:
The code itself:
if (formRenderSkipLogic.location == 'record_status_dashboard' && this.href == "javascript:;" && this.outerHTML.indexOf("triggerRTWSmappedField") != -1){ return; }
Well, I don't know if this workaround is the best solution, probably not, but its working.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
FRSL is not working in the Record Status Dashboard when Dynamic Data Pull (DDP) is enabled.
When DDP is enabled, it modifies the record table by adding an extra column as shown in the figure bellow.
This extra column appends one extra
<a>
element per row:The FRSL fails when Record Status Dashboard is opening. The following message is shown in the browser console:
This error is thrown when FRSL tries to process the
<a>
element that comes from the DDP code.After this error, the JS code stops and the module does not work as expected.
I coded a workaround for this problem that just ignores the
<a>
element that comes from DDP stuff:The code itself:
Well, I don't know if this workaround is the best solution, probably not, but its working.
The text was updated successfully, but these errors were encountered: