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

Community

Connector Improvement: SuccessFactors : Url in column instead of actual data

Answered
Atul Kala User

Hi Team,

We are using the SuccessFactors built-in connector to fetch data from several tables. We have observed that for some columns, instead of actual values, we are receiving a URL pointing to the data.
For example, in the JobApplicationStatusAuditTrail table, the jobApplication column returns a URL in the destination when using the built-in connector.

To retrieve the actual value for those columns, we are forced to use an SDK that calls the URL and fetches the data. Ideally, the built-in connector should provide a way to retrieve the actual values directly, rather than returning a URL.

Below is a snippet of the sdk code:
 
for rows in sf.get_batches(
            entity="JobApplicationStatusAuditTrail",
            select="revNumber, lastModifiedDateTime, lastModifiedBy, createdDateTime, skippedStatus, statusComments, createdBy, jobApplication, jobAppStatus",
            filter_="lastModifiedDateTime ge '" + last_updated_timestamp + "'",
            params={"$expand": "jobApplication, jobAppStatus"},
            batch_size=batch_size
    ):
 
 
We would like this functionality to be part of the inbuilt connector, allowing users to choose whether they want the actual data or the URL based on their needs.

Please let me know if you need more details.

Thanks,
Atul

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Sanjeevv Maniram T Fivetranner

    Hi Atul,

    Thank you for submitting this request. This is a valuable idea and aligns with the need for more flexible data retrieval options from the SuccessFactor connector. I have added your suggestion to our feature improvements backlog.

    To ensure we fully understand your requirements, could you share more about your use case and how retrieving the actual values (rather than URLs) would help with your data workflows? For example, are there specific downstream processes or reporting needs impacted by receiving just the URLs?

    We will keep the community updated on this thread with any progress regarding this improvement.

    Thanks,
    Sanjeevv