Folder and Mapping Issues
This page helps you troubleshoot issues with folder structures and table mappings in the SharePoint Connector.
Common Folder Issues
Folder Not Created
Symptoms:
- Expected folder doesn't exist
- FactBox shows empty or error
- Upload fails because no folder
Possible Causes and Solutions:
| Cause | Solution |
|---|---|
| No table mapping | Create mapping for the table |
| Mapping not active | Verify mapping configuration |
| No file uploaded yet | Upload a file to create folder |
| Permission issue | Check SharePoint permissions |
Wrong Folder Path
Symptoms:
- Documents in unexpected location
- Path different than expected
- Folder structure incorrect
Possible Causes and Solutions:
| Cause | Solution |
|---|---|
| Wrong Caption Field | Check Caption Field setting |
| Alternative mapping | Review alternative mapping priority |
| Parent mapping | Check parent table configuration |
| Base Folder wrong | Verify in SharePoint Setup |
Duplicate Folders
Symptoms:
- Multiple folders for same record
- Slightly different names
- Content split between folders
Possible Causes and Solutions:
| Cause | Solution |
|---|---|
| Name change | Record name changed after folder created |
| Mapping change | Configuration was modified |
| Special characters | Name sanitizing creates variations |
Mapping Issues
FactBox Not Appearing
Symptoms:
- No SharePoint FactBox on page
- Expected integration not visible
Possible Causes and Solutions:
| Cause | Solution |
|---|---|
| No table mapping | Create mapping for this table |
| Page not extended | May need page extension |
| Permissions | User may lack permissions |
| License | Check licensing status |
Wrong Table Mapping
Symptoms:
- Documents going to wrong location
- Unexpected folder structure
Diagnostic Steps:
- Open SharePoint Table Mapping
- Find entry for the table
- Verify configuration
- Check for alternative mappings
Inherited Mapping Not Working
Symptoms:
- Documents not inheriting parent folder
- Each document creating new folder
Possible Causes and Solutions:
| Cause | Solution |
|---|---|
| Wrong mapping method | Set to "Inherited Dynamic" |
| Parent mapping missing | Create mapping for parent table |
| Parent link field wrong | Verify Parent Link Field 1/2/3 |
| No parent record | Check record has valid parent |
Path and Naming Issues
Special Characters in Names
Symptoms:
- Folder creation fails
- Names appear differently
- Path errors
Solutions:
- Check Name Sanitizing setting in setup
- Use "Strict" for maximum compatibility
- Avoid problematic characters in BC data:
| - `# % & * : < > ? / \ | ` |
|---|
Path Too Long
Symptoms:
- Error creating folder
- Operations fail silently
- Path truncated
SharePoint Limits:
- Total path: ~400 characters
- Folder name: ~255 characters
Solutions:
| Action | How |
|---|---|
| Shorter names | Use shorter Caption values |
| Shallower nesting | Reduce folder depth |
| Abbreviate | Use codes instead of full names |
URL Encoding Issues
Symptoms:
- %20 appearing in paths
- Folders not found
- Path mismatch errors
Solutions:
- Don't use URL encoding in Base Folder
- Use actual spaces if needed
- Check for accidentally encoded values
Alternative Mapping Issues
Conditions Not Matching
Symptoms:
- Document going to wrong folder
- Alternative not being applied
Diagnostic Steps:
- Check field value matches exactly
- Verify priority order
- Test with known values
- Check for leading/trailing spaces
Priority Conflicts
Symptoms:
- Unexpected folder routing
- Sometimes correct, sometimes not
Solutions:
- Review all alternative mappings
- Ensure unique priorities
- Highest priority number wins -- give the most specific condition the highest priority
- Test each condition independently
Parent-Child Issues
Child Not Finding Parent
Symptoms:
- Document creates own folder
- Not using parent's folder
Possible Causes and Solutions:
| Cause | Solution |
|---|---|
| Parent Ref Field wrong | Set correct field number |
| Parent value empty | Check field has value |
| Parent not mapped | Create parent mapping |
| Parent folder missing | Create parent's folder first |
Multi-Level Inheritance
Symptoms:
- Deep hierarchy not resolving
- Folders in wrong location
Check:
- Each level has proper mapping
- Parent references are correct at each level
- All intermediate folders exist
Diagnostic Tools
Checking Active Mappings
- Go to Active SharePoint Mapping
- Find the record
- View the stored folder path
- Compare to expected path
Verifying Configuration
| Check | Location |
|---|---|
| Table mapping | SharePoint Table Mapping |
| Alternative mapping | Alternative Mapping list |
| Auto-create subfolders | Auto-Create Subfolders |
| Metadata | Mapping Metadata |
Testing Mapping
- Create a test record
- Upload a file
- Check where folder is created
- Verify path is correct
Resolution Steps
For Missing Folders
- Verify table mapping exists
- Check mapping configuration
- Verify SharePoint permissions
- Try uploading a file
- Check for error messages
For Wrong Paths
- Review Caption Field selection
- Check for alternative mappings
- Verify parent configuration
- Test with new record
For Inconsistent Behavior
- Document what's happening
- Check for recent configuration changes
- Review alternative mapping priorities
- Test systematically
Best Practices
Prevention
| Practice | Benefit |
|---|---|
| Test mappings | Catch issues early |
| Document configuration | Reference for troubleshooting |
| Use consistent naming | Predictable results |
| Review before changes | Understand impact |
When Making Changes
| Action | Consider |
|---|---|
| Changing Caption Field | Existing folders won't rename automatically; use Rename mapped folder on the Change Mapping page per record |
| Adding alternative | Check priority doesn't conflict |
| Changing parent | Child mappings affected |