Newly added custom fields on the account entity are not appearing in Advanced Find views or report filters after importing our latest solution package. We deployed a managed solution containing five new custom fields for account classification including industry segment, revenue tier, and strategic priority level.
The solution import completed successfully without errors and the custom fields are visible when viewing account records in the main form. Users can see and edit the field values directly on account records. However, when attempting to create filtered views using Advanced Find or build reports with these fields, they don’t appear in the available fields list.
We’ve verified that the custom field searchable property is enabled in the field definitions and view metadata appears updated in Solution Explorer. The fields have appropriate field-level security configured allowing our sales team full access. We need these fields available for reporting to segment accounts by strategic value for our quarterly business review. This is blocking critical executive reporting requirements. Has anyone experienced custom fields not appearing in query builders after solution imports?
Verify each user has appropriate profiles assigned
Use team-based assignment for easier management
Audit profile assignments quarterly
Testing Field Security:
Before deploying to production:
Test with user accounts from each security role
Verify fields appear/don’t appear as expected in:
Forms
Views
Advanced Find
Reports
API queries
Document expected behavior for each role
Field Security Impact on Reporting:
Users without Read permission:
Cannot see field in Advanced Find
Cannot add field to views
Cannot filter reports by field
See blank values if field included in shared views
Design reports considering field security:
Create role-specific report views
Document which reports require which security profiles
Provide alternative reports for restricted users
Additional Recommendations for Your Scenario:
Executive Reporting Requirements:
For your quarterly business review reports:
Create dedicated system views including all five custom fields
Name views clearly: ‘Accounts - Strategic Classification’
Set appropriate default sorting and filtering
Share views with executive team
Consider creating Power BI reports for richer visualization
Solution Deployment Checklist:
Add to your deployment process:
Pre-deployment: Verify Searchable property in source environment
During deployment: Monitor import progress for warnings
Post-deployment: Validate field properties match source
Post-deployment: Test Advanced Find with each security role
Post-deployment: Verify existing reports still function
Post-deployment: Update user documentation
User Communication:
When deploying new fields:
Notify users of new fields and their purpose
Provide training on how to use fields in Advanced Find
Share example queries/views demonstrating field usage
Document field definitions in internal wiki
Schedule Q&A session for power users
Ongoing Maintenance:
Quarterly review:
Audit which custom fields are actually being used in queries
Review field security assignments for role changes
Verify Searchable property still enabled on all fields
Check for orphaned field security profiles
Update documentation for any configuration changes
With these comprehensive practices, your custom fields will reliably appear in Advanced Find and reporting tools after solution imports. The combination of proper Searchable configuration, metadata refresh awareness, and appropriate field-level security setup ensures fields are both accessible to authorized users and properly integrated into the query and reporting infrastructure.
This draft is based on general Microsoft Dynamics 365 Sales knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
This usually happens when the ‘Searchable’ property isn’t set correctly on the custom fields. Even though you mentioned it’s enabled, double-check each field in the solution. Navigate to Settings > Customizations > Customize the System > Entities > Account > Fields, select each custom field, and verify the ‘Searchable’ checkbox is marked. If it wasn’t set in the original solution before export, importing won’t automatically enable it. You’ll need to update the fields and publish customizations.
I verified all five fields and the Searchable property is definitely enabled on each one. I also republished all customizations after confirming this, but the fields still don’t show up in Advanced Find. Could there be a caching issue or does the system need time to refresh the metadata after publishing?
Try clearing your browser cache and doing a hard refresh. Sometimes the Advanced Find interface caches the available fields list and doesn’t pick up recent changes. Also check if you’re using the legacy Advanced Find or the new Quick Find interface - they sometimes show different field lists during metadata refresh periods. If that doesn’t work, try accessing Advanced Find from a different browser or incognito mode to rule out client-side caching issues completely.
Confirmed this resolves the issue — after re-enabling the Searchable property on our custom Account fields post-solution import, they immediately appeared in Advanced Find without requiring a full republish.
Beyond caching, check the field security profiles assigned to your user account. Even with Searchable enabled, if field-level security is configured and your security profile doesn’t have ‘Read’ permission for these fields, they won’t appear in Advanced Find for you. Navigate to Settings > Security > Field Security Profiles and verify that the profile assigned to your user includes read access to all five custom fields. This is a common oversight when implementing field-level security on new custom fields.
I checked field security profiles and found the issue! The custom fields were added to a field security profile that restricts read access by default. I updated the security profile to grant read permission to the Sales Manager role and now the fields are appearing in Advanced Find. Clearing browser cache also helped ensure I was seeing the latest metadata.