Insight Report Developer Hub

On This Page

Access & Provisioning Guidance

Licensing & Allocation Limits

To ensure robust data governance and strictly manage named license constraints under the Power BI contract, each state agency is allocated up to two (2) designated Report Developers.

• All candidate developers must be officially nominated by their Agency Controller.

• Insight Report Developers will be provisioned with infoAdvantage (iA) developer access out of necessity to analyze legacy reports for conversion; however, requests strictly for standalone iA developer access will no longer be granted.

End-to-End Provisioning Workflow

1. Controller Nomination: The Agency Controller submits a nomination specifying up to two developers.

2. MA1 Non-Production (NPD) Access: The CORE Help Desk logs a ticket to provision Power BI licensing and MA1 Power BI Workspace access.

3. Training & Practical Review: Candidate completes training and practical assignments within 60 days.

4. Sign Statement of Agreement (SoA): Upon passing assignment review, a Statement of Agreement will be sent to the user to sign.

5. Production (PRD) Activation: After the SoA has been signed, CORE Operations requests PRD Power BI Workspace access through CGI for provisioning.

Training & Onboarding

Required Developer Onboarding Course

All nominated developers must complete the hands-on training for Report Developers.

• Completion Window: 60 Calendar Days from initial MA1 provisioning.

• Revocation Policy: Incomplete requests past 60 days are canceled, and MA1 Power BI access is revoked to free up development licenses.

• Training Material: Distributed directly after a request is made via CORE Help.

• Supplementary Technical Reference: For additional technical guidance on core tool functionalities, refer to the Microsoft Power BI Documentation.

Practical Validation Tasks (MA1 Environment)

To complete training, developers must build and save specific test files within their named developer subfolder in their department NPD workspace in Power BI.  Upon completion, developers must reply to their assigned ServiceHub ticket to request a CORE Operations review.

1:1 Conversion Support

1:1 Report Developer Conversion Assistance

Collaborative, 30-minute hands-on working sessions hosted by CGI and CORE Operations technical experts to solve blockers for agency custom reports.

• Booking Lead Time: Sessions open 1 week in advance to balance technical support capacity.

• Session Allowance: Limited to 1 session per developer at a time.

• Preparation Prerequisites: Developers must provide legacy infoAdvantage report details, file paths, and an active draft of the converted report in their Power BI workspace ready for review.

Insight Report Developer FAQs

Insight Report Developer Job Aids

Best Practices

Conversion Strategy Hierarchy

Before converting a legacy infoAdvantage report into a Power BI (Insight) report, developers must evaluate the request against the following hierarchy to optimize their agency's footprint:

• CORE Search Screens & Data Exports: Utilize native application grid exports whenever possible.

  • Standard Statewide Reports: Apply agency-specific prompts to existing standard reports.

    • Configurable Inquiries: Leverage user-built saved inquiry pages.

      • Custom Power BI Analytic/Paginated Reports: Reserve custom builds strictly for critical business logic.

• StateWide Report Copies: To request modifications to a standard Statewide report, developers must submit a request through the change management process.

• Convert Critical Need Only: Dedicate developer resources strictly to reports serving essential operations that cannot be satisfied via Search Screens, Standard StateWide Reports, or Configurable Inquiries.

Production (PRD) Promotion Pipeline

• Agency Testing: Develop and validate the report thoroughly within the MA1 UAT environment.

• Promotion Staging: Move the finalized report into the designated "Ready for Promotion to PRD" folder in MA1.

• Subfolder Assignment Ticket: Email core.help@state.co.us to submit a ServiceHub ticket specifying the exact target subfolder path within the department's RPRTLST directory where the report should be deployed.  Ticket requests must include confirmation from the agency's controller, budget, procurement, payroll, or HR director verifying that department UAT was completed and approval was granted to promote the report to PRD.

• Legacy Archiving: Following PRD promotion, the corresponding legacy infoAdvantage report is archived/restricted in PRD to encourage adoption.