Thread Details
  • State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 353 subscribers
  • Views 962 views
  • Users 0 members are here
Forum Actions
Related

API String filters now working as expected?

Joana H

Hi all!

I'm using the SugarCRM API and trying different queries.

As mentioned in the documentation we expect to filter all the columns exposed from the /metadata endpoint for each module.

What happens is that we don't have consistent behavior. If you try querying the Accounts module and try filtering with the "name" column, by utilizing the $contains, $starts, and $ends it works fine.

Suppose you try to run the same filers to another column like Assigned_User_Name. It ignores the filters, which is misleading.

Parents Reply Children
  • 0 in reply to Joana H

    Hello  

    You could attempt to reach out to support and perhaps post back on their answer so that everyone following the thread is updated about it.

    In general, I would not rely on anything that is not an actual field, to filter on.

    If I were you, I would look up which user id the specific user has, and then filter with something like this:

        "filter" : [
        {
            "assigned_user_id": {
                "$equals": "<the user guid id goes here>"
            }
        }
    ],

    Cheers

    --

    Enrico Simonetti

    Sugar veteran (from 2007)

    www.naonis.tech


    Feel free to reach out for consulting regarding:

    • API Integration and Automation Services
    • Sugar Architecture
    • Sugar Performance Optimisation
    • Sugar Consulting, Best Practices and Technical Training
    • AWS and Sugar Technical Help
    • CTO-as-a-service
    • Solutions-as-a-service
    • and more!

    All active SugarCRM certifications

    Actively working remotely with customers based in APAC and in the United States