Skip to main content
Version: Current

Troubleshooting: Data Dependencies Not Filtering Options Correctly

Problem​

When selecting a value in one field (the controlling field, e.g., Subsidiary), the options available in another field (the dependent field, e.g., Location or Supplier) are not being limited as expected based on the configured Data Dependencies.

Common Causes​

  1. Incorrect Dependency Configuration: The dependency rule itself is not set up correctly (e.g., wrong controlling resource selected, wrong dependent value linked).
  2. Dependency Not Saved: Changes made to dependencies were not saved correctly.
  3. Controlling Field Value Not Set: The controlling field (e.g., Subsidiary) on the transaction document is empty or not yet selected. Dependencies only apply after the controlling field has a value.
  4. Incorrect Controlling Field Value: The value selected in the controlling field does not match any configured dependency rule for the dependent field options.
  5. Caching Issues: Occasionally, the front-end might not have picked up the latest dependency configuration (less common).
  6. Inactive Records: The expected options in the dependent field might be marked as Inactive in Zudello, preventing them from appearing even if the dependency rule is correct.
  7. Misunderstanding of Logic: Dependencies limit options based on what's allowed. If no dependency is set for a specific controlling value, all active options for the dependent field might be shown (unless restricted by other means).

Troubleshooting Steps​

  1. Verify Dependency Configuration:
    • Navigate to Settings and find the dependent dimension (e.g., Locations).
    • Open the specific dimension value that should be appearing (e.g., Location "Warehouse A").
    • Click the Dependencies icon.
    • Verify that the correct controlling resource (e.g., Subsidiary) and the specific controlling value (e.g., Subsidiary "NSW") are linked here.
    • Check other related dimension values to ensure dependencies are set correctly across the board.
  2. Check Controlling Field on Document:
    • Open the transaction document where the filtering isn't working.
    • Ensure the controlling field (e.g., Subsidiary) has a value selected. If it's empty, select the appropriate value first.
    • Verify the correct value is selected in the controlling field.
  3. Check Dependent Value Status:
    • Navigate to Settings and find the dependent dimension list (e.g., Locations).
    • Ensure the dimension value you expect to see (e.g., "Warehouse A") is marked as Active.
  4. Refresh/Clear Cache: Do a hard refresh of your browser (Ctrl+Shift+R or Cmd+Shift+R) to clear cached data and try selecting the values again.
  5. Test with Simple Case:
    • Try selecting a different value in the controlling field for which you know a dependency exists. Does the dependent field filter correctly for that case? This helps isolate if the issue is with a specific dependency rule or the feature generally.
  6. Review Dependency Logic: Ensure you understand how the dependency is meant to work. Is it possible that for the selected controlling value, no specific dependency was set, meaning all active options should be displayed?

Need Help?​

If dependencies are consistently not filtering as expected after checking the configuration and data, contact Zudello support. Provide:

  • Screenshots of the dependency configuration for the relevant dimension values.
  • The Document UUID of an example transaction where filtering failed.
  • Details of the controlling field value selected and the expected vs. actual options shown in the dependent field.