# Basic sync rules with subfield

**URL:** <https://discuss.elastic.co/t/basic-sync-rules-with-subfield/368494>\
**Category:** Elastic Search\
**Tags:** connectors\
**Created:** [October 9, 2024, 6:23am UTC](https://discuss.elastic.co/t/basic-sync-rules-with-subfield/368494 "2024-10-09T06:23:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ankur\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankur_mathur/32/138191_2.png) [@Ankur\_Mathur](https://discuss.elastic.co/u/Ankur_Mathur)\
**Post date:** [October 9, 2024, 6:23am UTC](https://discuss.elastic.co/t/basic-sync-rules-with-subfield/368494/1 "2024-10-09T06:23:52Z")

</div>

Basic sync rules of fields having subfield is not working. For example If there is an object field `manager` with a subfield `age` , then a basic rule to exclude `manager.age > 30` is not workig. What could be wrong here?

---

<div class="post-metadata">

**Author:** ![Jedr\_Blaszyk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jedr_blaszyk/32/127637_2.png) [@Jedr\_Blaszyk](https://discuss.elastic.co/u/Jedr_Blaszyk)\
**Post date:** [October 9, 2024, 8:57am UTC](https://discuss.elastic.co/t/basic-sync-rules-with-subfield/368494/2 "2024-10-09T08:57:53Z")

</div>

Hey @Ankur_Mathur Our [docs](https://www.elastic.co/guide/en/enterprise-search/current/sync-rules.html) don’t mention accessing nested fields for basic sync rules. To confirm, I checked the [implementation](https://github.com/elastic/connectors/blob/a109c26cf4afee6ddb45402a855515bb8ca014b0/connectors/filtering/basic_rule.py#L283), and unfortunately, we currently don’t support dot notation for nested field lookups.

One potential workaround is to customize the [ingest pipeline](https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html) for your connector. In the Pipeline tab within the connector window, you can modify the ingest pipeline. On the edit pipeline screen, you can add a `Drop` processor to filter out documents based on specific conditions. I’ve attached a screenshot for reference.

 ![Screenshot 2024-10-09 at 10.50.20](https://us1.discourse-cdn.com/elastic/original/3X/6/6/66899732360da50e8983f43dd401e692ec050313.jpeg)

If you believe supporting nested field lookups for basic sync rules would be a valuable enhancement for connectors, feel free to submit an enhancement request as an issue in [GitHub - elastic/connectors: Source code for all Elastic connectors, developed by the Search team at Elastic, and home of our Python connector development framework](https://github.com/elastic/connectors) 🙂

---

<div class="post-metadata">

**Author:** ![Ankur\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankur_mathur/32/138191_2.png) [@Ankur\_Mathur](https://discuss.elastic.co/u/Ankur_Mathur)\
**Post date:** [October 9, 2024, 10:42am UTC](https://discuss.elastic.co/t/basic-sync-rules-with-subfield/368494/3 "2024-10-09T10:42:18Z")

</div>

thanks @Jedr_Blaszyk for you response. I have tried with ingest pipeline and it works fine. BTW elastic support assistant informs that its possible to use nested fields lookups.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 6, 2024, 10:43am UTC](https://discuss.elastic.co/t/basic-sync-rules-with-subfield/368494/4 "2024-11-06T10:43:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.