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

Community

Concur expansion ot travel_request table

Answered
Hardy Titz User

Connector name: Concur

Table name: travel_requests

Column to add:

  • report_ID
  • Owner_name
  • owner_login_id
  •  

 

Additional details: Our objective would be to have an overview of reports that were not requested through the "Travel" module.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Tom Jose Fivetranner

    Hi Hardy,

    This request to expand the travel_requests table in the Concur connector is noted and added to our feature improvements backlog. Including columns like report_ID, owner_name, and owner_login_id could help provide deeper insights.

    To better understand your requirements, could you provide more details on the specific reporting or analytics challenges you are facing? Are there particular workflows that are impacted by not having these columns? Any insights into how you plan to use this data will help us evaluate the request further.

    We will use this thread to update the community on any progress.

    Thanks,
    Tom

  • Hardy Titz User

    Our internal policy requires all business travels to be requested and pre-approved through the Travel module. In reality this is not always the case and we see examples where travel expenses are only recorded as part of normal expense reports. As of now there is no way to link these together and have visibility on which "expense reports" had a pre approved travel request.

    Could you please provide us with a timeline on when could we expect this enhancement? Ideally we would need it by end of May.