Skip to main content

Community

Connector Improvement: Mavenlink - Include Vendors for expenses

Answered

Please sign in to leave a comment.

Comments

3 comments

  • Official comment

    Hi Simon - 

    Thanks so much for submitting this feature request. Would you mind sharing what specific "other" fields you're interested in and what your use case would be for using them? This will help the Product team better prioritize your request.

    Best,

    Erin 

    Hi Erin, 

    Sorry for the late answer, I came back here since this would still be useful for us. Here are the useful attributes that the API documentation shows as available:  

    • The vendor is for sure the missing field that is the most obvious and essential. 
    • approved
    • submitted, active_submission and recent_submission: these help in indicating if an expense is current or not (e.g. submitted and pending approval, cancelled, etc.) In fact, I just realized that Fivetran seems not to sync Expense Report Submissions at all. Although these are not crucial for our use (provided we know if an expense is approved), expense reports are integral to ML's business logic so this is more about keeping Fivetran's connector up to date with ML. 
    • reimbursable: indicates if the expense is a vendor on an employee expense.

    Here you are, hope this helps!

    Dear Erin,

    Do you have any update regarding this feature request?

    The missing Expense Report Submissions in the API calls is currently preventing us from identifying the status of each expense and filter accordingly to our needs, although this data is avaiblable in Mavenlink's API under the GET request "https://api.mavenlink.com/api/v1/expense_report_submissions?all_on_account=true
    (https://developer.mavenlink.com/beta/#tag/Expense-Report-Submissions%2Fpaths%2F~1expense_report_submissions%2Fget).

    In addition to this data, the already synced Expenses should include the active_submission and recent_submission fields as these are included by default in the API response but look ignored in the "create_staging_table" Fivetran event.

    Looking forward to hearing from you,