Thread Details
  • State Not Answered
  • +1 person also asked this people also asked this
  • Replies 12 replies
  • Subscribers 373 subscribers
  • Views 315 views
  • Users 0 members are here
Forum Actions
Related

Some help getting started with using FilterAPI to create sudo reports in n8n please

Adam Ososki

I am using n8n - I can pull a very basic field restricted list from accounts (for example) using this 
/rest/v11_16/Accounts/filter?max_num=50&order_by=id%3ADESC&fields=id,name

But I haven't been able to work out where to build more complex filters spanning multiple related modules.

I'm not able to work out where to put the Filter expressions like you show in examples - query params, header, body etc 

filter=[{"name":"Nelson Inc"}] going in Header / Body

what type is it expecting

would you do a new field for every filter or build them into one huge expression.

So far I haven't found a place that i can enter even a single name filter and return on that. 



Any help or pointers you can give to get started would be great - as I imagine I will have to try and recreate the massive / complex reports that the data guys are building in Sugar in this filterapi...

We need to replicate a pretty complex report with lots and lots of joins across main modules / custom modules etc - my data guys here are saying this approach won't work at all because there are so many joins - and something about there being hidden helper tables that connect for example accounts to contacts - with over 400k rows - so not sure if we need to reference the hidden helpers or direct accounts to contacts relationship. Also if You are using for example Opportunities as the starting module, then you want to get the contacts who can be linked to multiple accounts  - so its 2 or 3 layers deep effectively - how does that work with field relationship naming....?

(I am advanced Sugar user - wrote most of the original reports used in the business - but newish to api's)

  • 0 Sugar Employee Badge in reply to Adam Ososki

    Hi  , sorry for the delay, we had a holiday here in Germany. 
    As for the related fields, you need to have it as part of the module to request it. For example you can request account_name field from the Opportunities, while account_name is a relate field built on top of the relationship between Opportunities and Accounts modules. Long story short, you need those relate fields types to request them as part of the filter output. So it's definitely not that you can request ANY field from the related module based on the relationship (so filter API is not equal to Reports).

    If you could provide some real-world example of the fields you are looking for, I could give you a sample of the request or some extra code to create a relate field based on the existing.

  • 0 in reply to Constantine Shpikat

    Thanks   but they are huge linked reports with multiple related fields and joins. I think they will have to amend the run times manually until either we get the data warehouse or we upgrade to a version that supports the api you suggested at the start

    You assistance on this was really appreciated though.