Compliance Dashboard — Dataverse Schema Reference¶

Option Sets¶

Deployment requirement — explicit integer values: Every option set below uses small integer values (1-6) rather than the Dataverse default 100000000+ allocation. Sample data, DAX measures, flow pseudo-code, and scripts/load_sample_data.py all assume the values below. When you create these option sets, you MUST set the integer values explicitly via the Web API or the Power Apps maker portal's advanced options — accepting the default 100000000+ allocation will silently break every DAX measure and sample-data import. See docs/dax-measures.md for the same warning on the DAX side.

Governance Pillar (`fsi_cd_pillar`)¶

Value	Label
1	Security
2	Management
3	Reporting
4	SharePoint

Control Category (`fsi_cd_category`)¶

Value	Label
1	Native Microsoft Feature
2	Custom Solution Required
3	Process/Documentation Control

Compliance Status (`fsi_cd_status`)¶

Value	Label
1	Compliant
2	Partial
3	Non-Compliant
4	Not Applicable

Governance Zone (`fsi_cd_zone`)¶

Value	Label
1	Zone 1 - Personal Productivity
2	Zone 2 - Team Collaboration
3	Zone 3 - Enterprise Managed

Exception Severity (`fsi_cd_severity`)¶

Value	Label
1	Critical
2	High
3	Medium
4	Low

Exception Status (`fsi_cd_exceptionstatus`)¶

Value	Label
1	Open
2	In Progress
3	Pending Verification
4	Closed
5	Accepted Risk

SLA Status (`fsi_cd_slastatus`)¶

Value	Label
1	On Track
2	At Risk
3	Breached

Evidence Type (`fsi_cd_evidencetype`)¶

Value	Label
1	Screenshot
2	Configuration Export
3	Audit Log
4	Policy Document
5	Test Result
6	External Report

Migration note (option-set values 1-6 vs. Dataverse 100000000+): Migration of fsi_cd_evidencetype to 100000000-based values is deferred. cross-solution-integration/scripts/powershell/IntegrationConfig.psm1 hardcodes $script:EvidenceTypeTestResult = 5 (mapping to Test Result). Renumbering this option set requires a coordinated minor-bump cycle with the cross-solution-integration solution. Until that coordinated change ships, create this option set with the explicit integer values listed above (1-6) when deploying via Web API; do not rely on the Power Apps maker portal's default 100000000+ allocation. See repo CLAUDE.md §9 (Option-set values) for the cross-solution policy.

Tables¶

Control Master (`fsi_ControlMaster`)¶

Logical Name: fsi_controlmaster
Ownership: Organization
Description: Master list of 78 FSI Agent Governance Framework controls

SchemaName	Logical Name	Type	Required	Description
fsi_ControlId	fsi_controlid	String(10)	Yes	Control identifier (e.g., 1.1, 2.12)
fsi_Name	fsi_name	String(200)	Yes	Control display name (primary column)
fsi_Pillar	fsi_pillar	Choice (fsi_cd_pillar)	Yes	Governance pillar (1-4)
fsi_Description	fsi_description	Memo(4000)	No	Control description
fsi_Zone1Applicable	fsi_zone1applicable	Boolean	Yes	Applicable to Zone 1
fsi_Zone2Applicable	fsi_zone2applicable	Boolean	Yes	Applicable to Zone 2
fsi_Zone3Applicable	fsi_zone3applicable	Boolean	Yes	Applicable to Zone 3
fsi_RegulatoryReference	fsi_regulatoryreference	String(500)	No	Related regulations (FINRA, SEC, etc.)
fsi_Weight	fsi_weight	Decimal	Yes	Control weight for scoring (1.0-3.0)
fsi_Category	fsi_category	Choice (fsi_cd_category)	No	Control category classification

Control Assessment (`fsi_ControlAssessment`)¶

Logical Name: fsi_controlassessment
Ownership: User
Description: Assessment records for each control, capturing compliance status

SchemaName	Logical Name	Type	Required	Description
fsi_ControlMasterId	fsi_controlmasterid	Lookup (fsi_controlmaster)	Yes	Reference to control master
fsi_AssessmentDate	fsi_assessmentdate	DateTime	Yes	Date of assessment
fsi_Status	fsi_status	Choice (fsi_cd_status)	Yes	Compliance status
fsi_Zone	fsi_zone	Choice (fsi_cd_zone)	Yes	Governance zone being assessed
fsi_Score	fsi_score	Integer	Yes	Numeric score (0, 50, 100)
fsi_Assessor	fsi_assessor	Lookup (systemuser)	Yes	Person who performed assessment
fsi_Notes	fsi_notes	Memo(4000)	No	Assessment notes
fsi_NextReviewDate	fsi_nextreviewdate	DateTime	No	Scheduled next review date
fsi_EvidenceCount	fsi_evidencecount	Integer	No	Number of linked evidence items

Compliance Score (`fsi_ComplianceScore`)¶

Logical Name: fsi_compliancescore
Ownership: Organization
Description: Daily compliance score snapshots for trend analysis

SchemaName	Logical Name	Type	Required	Description
fsi_ScoreDate	fsi_scoredate	Date	Yes	Score calculation date
fsi_OverallScore	fsi_overallscore	Decimal	Yes	Overall compliance score (0-100)
fsi_Pillar1Score	fsi_pillar1score	Decimal	No	Security pillar score
fsi_Pillar2Score	fsi_pillar2score	Decimal	No	Management pillar score
fsi_Pillar3Score	fsi_pillar3score	Decimal	No	Reporting pillar score
fsi_Pillar4Score	fsi_pillar4score	Decimal	No	SharePoint pillar score
fsi_Zone1Score	fsi_zone1score	Decimal	No	Zone 1 compliance score
fsi_Zone2Score	fsi_zone2score	Decimal	No	Zone 2 compliance score
fsi_Zone3Score	fsi_zone3score	Decimal	No	Zone 3 compliance score
fsi_CompliantCount	fsi_compliantcount	Integer	Yes	Count of compliant controls
fsi_PartialCount	fsi_partialcount	Integer	Yes	Count of partially compliant controls
fsi_NoncompliantCount	fsi_noncompliantcount	Integer	Yes	Count of non-compliant controls
fsi_ExceptionCount	fsi_exceptioncount	Integer	Yes	Count of open exceptions

Compliance Exception (`fsi_ComplianceException`)¶

Logical Name: fsi_complianceexception
Ownership: User
Description: Open compliance exceptions requiring remediation

SchemaName	Logical Name	Type	Required	Description
fsi_Name	fsi_name	String(200)	Yes	Exception title (primary column)
fsi_ControlAssessmentId	fsi_controlassessmentid	Lookup (fsi_controlassessment)	Yes	Related assessment
fsi_Severity	fsi_severity	Choice (fsi_cd_severity)	Yes	Exception severity (Critical/High/Medium/Low)
fsi_ExceptionStatus	fsi_exceptionstatus	Choice (fsi_cd_exceptionstatus)	Yes	Exception lifecycle status
fsi_Owner	fsi_owner	Lookup (systemuser)	Yes	Assigned remediation owner
fsi_Description	fsi_description	Memo(4000)	Yes	Exception description
fsi_RootCause	fsi_rootcause	Memo(4000)	No	Root cause analysis
fsi_RemediationPlan	fsi_remediationplan	Memo(4000)	No	Planned remediation steps
fsi_TargetDate	fsi_targetdate	Date	Yes	Target remediation date
fsi_ActualCloseDate	fsi_actualclosedate	Date	No	Actual close date
fsi_DaysOpen	fsi_daysopen	Integer	No	Days exception has been open (calculated)
fsi_SlaStatus	fsi_slastatus	Choice (fsi_cd_slastatus)	No	SLA status (On Track/At Risk/Breached)

Compliance Evidence (`fsi_ComplianceEvidence`)¶

Logical Name: fsi_complianceevidence
Ownership: User
Description: Evidence items linked to assessments for audit purposes

SchemaName	Logical Name	Type	Required	Description
fsi_Name	fsi_name	String(200)	Yes	Evidence title (primary column)
fsi_ControlAssessmentId	fsi_controlassessmentid	Lookup (fsi_controlassessment)	Yes	Related assessment
fsi_EvidenceType	fsi_evidencetype	Choice (fsi_cd_evidencetype)	Yes	Type of evidence
fsi_SourceUrl	fsi_sourceurl	String(2000)	No	Link to evidence source
fsi_EvidenceDescription	fsi_evidencedescription	Memo(4000)	No	Evidence description
fsi_CollectedDate	fsi_collecteddate	DateTime	Yes	Date evidence was collected
fsi_CollectedBy	fsi_collectedby	Lookup (systemuser)	Yes	Person who collected evidence
fsi_Hash	fsi_hash	String(64)	No	SHA-256 hash for integrity verification

Relationships¶

Parent Table	Child Table	Relationship
fsi_controlmaster	fsi_controlassessment	1:N
fsi_controlassessment	fsi_complianceexception	1:N
fsi_controlassessment	fsi_complianceevidence	1:N

Auto-generated from create_cd_dataverse_schema.py schema definitions.

Compliance Dashboard — Dataverse Schema Reference¶

Option Sets¶

Governance Pillar (fsi_cd_pillar)¶

Control Category (fsi_cd_category)¶

Compliance Status (fsi_cd_status)¶

Governance Zone (fsi_cd_zone)¶

Exception Severity (fsi_cd_severity)¶

Exception Status (fsi_cd_exceptionstatus)¶

SLA Status (fsi_cd_slastatus)¶

Evidence Type (fsi_cd_evidencetype)¶