It sounds like you’re having an issue with the InterWeave SmartSolutions icon (for 30/60/90-day tracking) not updating in your Salesforce (SF) accounts. This might be caused by a few different factors:
1. Data Syncing Issues
- The icons might not be updating if there is a problem with the data synchronization between Salesforce and InterWeave. Double-check the syncing configurations, schedules, and logs to see if any errors are reported.
2. API Integration Errors
- If the SmartSolutions is integrated with Salesforce via an API, it could be encountering issues during the update process. Ensure that the API calls are being made correctly and that there are no errors in the logs from the integration tool.
3. Field Updates and Conditions
- The icons might depend on certain fields (such as date fields for 30/60/90-day tracking) being updated correctly. Make sure the underlying conditions for updating the icon are being met. Check field update rules or triggers that might be controlling the visibility of these icons.
4. Permission and Access Issues
- If the icon visibility is tied to certain permissions, make sure that the necessary profiles or permission sets have access to view and update these fields. Verify the field-level security and page layouts.
5. Workflow or Automation Delays
- If workflows or automated processes are responsible for updating the 30/60/90 icons, there could be a delay or error in the automation. Check your process builder, workflow rules, or flow automation to ensure they are functioning as expected.
6. InterWeave Configuration
- Double-check the settings in InterWeave SmartSolutions. There might be custom configurations for how and when these icons are updated. Ensure that the configurations are set to trigger updates for the 30/60/90 days correctly.
Troubleshooting Steps:
- Check integration logs in both Salesforce and InterWeave.
- Review the last successful update of the icons.
- Ensure fields in Salesforce that drive the 30/60/90-day logic are updating correctly.
- Contact InterWeave support if the issue persists after reviewing logs and configurations.
Let me know if you need specific guidance on any of these steps!