KamoCRM

Use feature type name as key before numeric id in org feature preprocessing

Fixkamo-internal
Shipped
19 மார்ச், 2026 அன்று 6:13 PM UTC
Author
kamo
Commit
af4fdaf

Java returns features with `type: "VOIP"` and a numeric `id`. The preprocessing chain had `obj.id` before `obj.type`, causing all features to get numeric string keys instead of semantic names like VOIP/CRM/EMAIL. Swapped priority so `obj.type` is evaluated before `obj.id`. Also added `recordState.isActive` to the enabled resolution chain.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing