Hello,
EspoCRM support referred this question to Developer Help. We are evaluating EspoCRM Cloud 10.1.1 (Trial), using fictional data only. This is the vendor-hosted Cloud service, not a self-hosted installation.
We need server-enforced uniqueness that remains effective when API requests arrive simultaneously:
1. Channel identity (CRc76Identity):
(channel, business_ref, provider_ref)
Fields: (cRc76Channel, cRc76BusinessRef, cRc76ProviderRef).
2. Opportunity:
(contact_id, course_id, cycle_id)
Fields: (cRc76ContactId, cRc76CourseId, cRc76CycleId).
One contact may have separate opportunities for different courses or cycles.
3. External event (CRc76Event):
cRc76EventId and cRc76IdempotencyKey must EACH be independently unique, not merely unique as a pair.
For the two composite keys, we can alternatively store a canonical SHA-256 key in cRc76CompositeKey, provided a server-enforced UNIQUE constraint is supported.
We found the database-index metadata documentation, but the native Varchar creation form has no UNIQUE control and our Entity Manager menu only offers Export. We have not saved this prototype configuration yet.
Questions:
- What supported mechanism enforces these constraints atomically in EspoCRM Cloud, including when duplicate-check bypass flags are supplied?
- How can it be configured or deployed in Cloud? If it requires custom metadata, a hook, or an extension, can the Cloud provider install and maintain it?
- Is this available during Trial? Does it require a specific plan, provider intervention, or additional charges?
- What happens to soft-deleted records and null/empty key components, and what API response should a losing concurrent request receive?
A search-before-create workflow, an overridable duplicate warning, or a client-side lock alone would not meet the requirement: two concurrent requests must not both create the same identity, opportunity, or external event.
We would appreciate a Cloud-supported implementation path or a clear explanation of the limitation. No instance changes or paid services are requested by this post.
Thank you.
EspoCRM support referred this question to Developer Help. We are evaluating EspoCRM Cloud 10.1.1 (Trial), using fictional data only. This is the vendor-hosted Cloud service, not a self-hosted installation.
We need server-enforced uniqueness that remains effective when API requests arrive simultaneously:
1. Channel identity (CRc76Identity):
(channel, business_ref, provider_ref)
Fields: (cRc76Channel, cRc76BusinessRef, cRc76ProviderRef).
2. Opportunity:
(contact_id, course_id, cycle_id)
Fields: (cRc76ContactId, cRc76CourseId, cRc76CycleId).
One contact may have separate opportunities for different courses or cycles.
3. External event (CRc76Event):
cRc76EventId and cRc76IdempotencyKey must EACH be independently unique, not merely unique as a pair.
For the two composite keys, we can alternatively store a canonical SHA-256 key in cRc76CompositeKey, provided a server-enforced UNIQUE constraint is supported.
We found the database-index metadata documentation, but the native Varchar creation form has no UNIQUE control and our Entity Manager menu only offers Export. We have not saved this prototype configuration yet.
Questions:
- What supported mechanism enforces these constraints atomically in EspoCRM Cloud, including when duplicate-check bypass flags are supplied?
- How can it be configured or deployed in Cloud? If it requires custom metadata, a hook, or an extension, can the Cloud provider install and maintain it?
- Is this available during Trial? Does it require a specific plan, provider intervention, or additional charges?
- What happens to soft-deleted records and null/empty key components, and what API response should a losing concurrent request receive?
A search-before-create workflow, an overridable duplicate warning, or a client-side lock alone would not meet the requirement: two concurrent requests must not both create the same identity, opportunity, or external event.
We would appreciate a Cloud-supported implementation path or a clear explanation of the limitation. No instance changes or paid services are requested by this post.
Thank you.
