Support filtering by linked ID in Find Records module in Make.com
in progress
Dan Leeman
If you want to search by an ID, i.e.:
66a5e70966c030a478492943
“66a5e70966c030a478492943”
[66a5e70966c030a478492943]
[“66a5e70966c030a478492943"]
You can't do this with the OOTB Find Records module. Instead, you need to use the Custom HTTP requests or make a lookup in SmartSuite for the ID and compare the two.
Given the number of times one has to do this for a project it is cumbersome.
Jon Darbyshire
in progress
Jon Darbyshire
Thank you for posting, Dan Leeman! I have a few more questions for you:
- Can you provide more context on the frequency and scenarios in which you need to search by an ID?
- Are there any specific features or functionalities you would like to see in the improved Find Records module?
- Could you describe any challenges or limitations you've experienced with the current Custom HTTP requests or SmartSuite lookup methods?
Dan Leeman
Jon Darbyshire, great questions.
1) Finding records by a linked record ID is a super frequent use case. Examples: I want to find Tasks by Project, or Projects by Customer, or Contacts by Account. To minimize your JSON loads (which is reasonable, and the standard approach) requesting the parent object only returns an array of IDs. To actually get the core data about each task, one needs to query this way.
An alternate approach would be to have an endpoint that allows us to search by a list of IDs, but I think the first approach is more common.
2) I don't know what the lift is, but in general, I would like to see all fields be first-class citizens across UI/supported iPaaS/API. It's quite confusing when field A is only supported in the UI, field B is supported in a Make/Zapier module, and field C is accessible via the API but not Make/Zapier.
3) Yes, there are several key challenges: a) The logging is quite poor. When there is an error, I just get a 404 or 400 with no real description - making it very difficult to decipher the core issue at play. Then I have to test the same requests via another tool like Postman to verify the issue.
b) IMHO, the experience for inputting a JSON body in Make is terrible. It's a text area input. It messes up formatting, it's hard to read. Combined with (A), I have no idea if the JSON is causing an issue or something else.
c) Using the Custom HTTP vs. SmartSuite HTTP is even more annoying, because despite me authing, etc., now I still have to enter Account-Id and Auth info, it just takes more time.
I'd prefer to never use Custom HTTP with SmartSuite, and that SmartSuite HTTP is for specialized use cases, not as the common workaround to the core module not working.