Bug 270 - Insights/Scheduler - Period In Job Name

Cory Fifield -

Found in Version
Resolved in Version (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:

  1. Create a job to export to insights.
  2. Save job / execution with period ( . ) in the name
  3. Run the job
  4. Go to Insights and Add A Page
  5. 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.




Have more questions? Submit a request