Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: [Oracle BICC FSCM] Don't Overwrite Data Store Query Filters

Answered
Jude Anderson User

The current behavior of the Oracle BICC FSCM connector will delete or replace any query filter placed on the data store itself. This makes it impossible to reduce the amount of data read and extracted and has major impacts to performance and time to refresh data to our data warehouse. For example, one data store we want data from has a row for each 'organization' that an item belongs to, but we only want the data for the global item master organization. This means that we are returning and loading upwards of 200 times the amount of rows actually needed.

Please change the sync strategy to append to instead of replacing the BICC data store query filter. Thanks!

data store filter applied:

fivetran extract job replacing instead of appending to query filter:


 

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Frank Fivetranner
    • Edited

    Hi Jude, 

    We conducted testing on our end and found that the filters applied were not being returned by the datastore metadata API and did not reflect in the extract output. This seems to be a limitation on the Oracle side and means that we cannot support filters entered in the datastore. 

    However, we are slowly rolling out filtering capabilities to all connectors which should provide a workaround for Oracle Fusion users in the future. 

    Thanks, 

    Frank

  • Frank Fivetranner
    • Edited

    Hi Jude, 

    Thanks for submitting this request. This makes sense to me and I will pass this along to our engineering teams to investigate if it's possible to not overwrite the filters. 

    Frank