You’re offline. This is a read only version of the page.
While building a Physician Onboarding portal using Power Pages + Dataverse + SharePoint, I encountered multiple challenges around uploading documents for different document types (PAN Card, Aadhaar, Experience Letter, Address Proof, etc.).
Although Power Pages provides attachment support, multi-document, multi-step onboarding scenarios are not as straightforward as they appear from the UI. This post shares what I tried, what worked partially, what failed, and the key limitations that are not clearly documented.
My goal is to help others avoid spending time on approaches that look supported but break at runtime.
Power Pages basic form
Creates a new record
Attachments enabled
Storage: Dataverse Notes / SharePoint integration
✔ Record is created
✔ Files upload successfully
All documents are uploaded as generic attachments
No way to map specific files to specific document types
Not usable when compliance requires explicit document categorization
Conclusion:
Works technically, but not suitable for structured onboarding.
Step 1: Physician details
Step 2: Document upload
Expected to pass record ID between steps
❌ File upload fails with messages like:
“This record hasn’t been created yet”
“File doesn’t match file storage configuration”
“Maximum 0 files allowed”
Power Pages does not reliably pass the Dataverse record ID
between steps in a way attachments can use
Attachments require an existing Dataverse record
This dependency is not clearly stated in UI guidance
Conclusion:
Multi-step UX + attachments looks supported, but breaks in practice.
Page 1: Create Dataverse record
Redirect to Page 2 with record ID in query string
Page 2: Upload documents
⚠ Inconsistent behavior
Query string ID is not always recognized by attachment control
Upload fails with storage configuration errors
Fragile implementation, not reliable for production
Conclusion:
Technically possible with heavy customization, but not stable.
| Field Name | Data Type |
|---|---|
| PAN Card | File |
| Aadhaar Card | File |
| Experience Letter | File |
| Address Proof | File |
✔ Clear mapping
✔ Each field accepts one file
Each File column supports only one file
No support for:
Re-uploads
Multiple documents per category
Real-world onboarding scenarios
Conclusion:
Works technically, but not suitable for scalable onboarding use cases.
Attachments require a Dataverse record to exist
Multi-step forms do not support file uploads reliably
Attachments cannot be bound to specific document categories
SharePoint integration validation ≠ attachment readiness
File size errors often mask record ID / storage binding issues
These behaviors are learned through trial, not surfaced clearly in Power Pages UX or documentation.
Despite server-based SharePoint integration being correctly configured and validated, Power Pages does not natively support:
Multi-document uploads
Categorized document handling
Multi-step onboarding with attachments
without significant trade-offs or custom development.
Is there a recommended Microsoft pattern for multi-document onboarding?
Are there roadmap updates planned for:
Step-aware attachments?
Document category mapping?
Has anyone successfully implemented this using supported patterns only?
Power Pages is excellent for simple data capture, but document-heavy onboarding workflows require careful architectural decisions. I hope this breakdown saves time for others evaluating Power Pages for similar use cases.
Looking forward to insights from the community
Share
Report
All responses (
Answers (
8,497
