Skip to main content
Solved

ETM - Get Building using Address Line1

  • March 10, 2023
  • 4 replies
  • 112 views

Forum|alt.badge.img+7

We have an ETM Channel where we want to fetch a n existing Building in Database using “Address1”.

Basically, the details that we can use to fetch Building Short Code are:

  1. Address 1
  2. Postal Code

We don’t see any lookup filter for Address1. Is there any work around? 

Best answer by Paul McCulloch

You can fetch a list of possible Building’s into a variable, then loop through that list for the one that matches. Postcode is a supported criteria in 1.5 - so we can use that to limit the list of possible buidlings:

I haven’t tested this - so there may be syntax errors , but the concept will work. 

You don’t need to do the looping in a separate variable. You could do it directly in another field. For example here’s how the default location for the matching building could be specified:

This avoids the need to do any other assyst searches (other than the buildings for a post code) - so should be fast & efficient.

4 replies

Forum|alt.badge.img+12
  • Hero (Customer)
  • 145 replies
  • March 13, 2023

I don't see this in ETM 1.5, but it does seem to be a new feature in ETM 1.6.


Forum|alt.badge.img+11
  • Hero (Employee)
  • 90 replies
  • March 14, 2023

This is a bug, fixed in ETM 1.6 - “Query Parameters that are not fields on the target REST resource are now available to select as Search Criteria.”


Forum|alt.badge.img+7
  • Author
  • Do Gooder (Customer)
  • 20 replies
  • March 15, 2023

Is there any workaround in version 11.5. We are upgrading to 11.6 later this year and till that time we need a solution.


Forum|alt.badge.img+11
  • Hero (Employee)
  • 90 replies
  • Answer
  • March 16, 2023

You can fetch a list of possible Building’s into a variable, then loop through that list for the one that matches. Postcode is a supported criteria in 1.5 - so we can use that to limit the list of possible buidlings:

I haven’t tested this - so there may be syntax errors , but the concept will work. 

You don’t need to do the looping in a separate variable. You could do it directly in another field. For example here’s how the default location for the matching building could be specified:

This avoids the need to do any other assyst searches (other than the buildings for a post code) - so should be fast & efficient.