Bug 270 - Insights/Scheduler - Period In Job Name
Found in Version 10.0.22.0
Resolved in Version 10.0.31.0 (Released: January 12, 2021)
Bug: Using a job or execution that has a period ( . ) in the name results in error when trying to bind a control in insights.
Steps to reproduce:
- Create a job to export to insights.
- Save job / execution with period ( . ) in the name
- Run the job
- Go to Insights and Add A Page
- Try to bind a control using the new job.
Expected Result: File name should not impact binding controls in Insights.
Actual Result: Error when attempting to bind a control in Insights that references job with period in the name.
Please sign in to leave a comment.