Skip to content

Updated docs to include remote key-mapping out of sync side effect #9325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: development
Choose a base branch
from

Conversation

adeel2023
Copy link
Contributor

No description provided.

@adeel2023 adeel2023 force-pushed the odata-remote-keymapping branch from 471b07e to 8941a75 Compare April 9, 2025 06:34
@quinntracy
Copy link
Collaborator

Hi @adeel2023 is this tied to the upcoming 10.22 release, or can it be merged after review?

@adeel2023
Copy link
Contributor Author

@quinntracy it can go in 10.23

@@ -193,5 +193,6 @@ Furthermore, external entities cannot be committed. Use the [Send External Objec
* The **Commit** activity does not work. Use **Send External Object** instead.
* On pages, the [Save button](/refguide/button-widgets/) and the [Save Changes event](/refguide/on-click-event/#save-changes) do not work when the page contains widgets that update external entities. Call a microflow that persists the changes using **Send External Object** instead.
* When synchronizing remote entities to an offline-first client while the remote service is offline, the synchronization will fail and users will see an error.
* Deleting an object of a published entity (which may be consumed as an external entity) and recreating it with the same OData key can lead to discrepencies.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add how services are supposed to resolve this? e.g. entities that are supposed to be deleted and recreated should use soft delete.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated.

@@ -193,5 +193,6 @@ Furthermore, external entities cannot be committed. Use the [Send External Objec
* The **Commit** activity does not work. Use **Send External Object** instead.
* On pages, the [Save button](/refguide/button-widgets/) and the [Save Changes event](/refguide/on-click-event/#save-changes) do not work when the page contains widgets that update external entities. Call a microflow that persists the changes using **Send External Object** instead.
* When synchronizing remote entities to an offline-first client while the remote service is offline, the synchronization will fail and users will see an error.
* Deleting an object of a published entity (which may be consumed as an external entity) and recreating it with the same OData key can lead to discrepencies.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Deleting an object of a published entity (which may be consumed as an external entity) and recreating it with the same OData key" - I'm not sure readers will understand what this means

Copy link
Collaborator

@quinntracy quinntracy Apr 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joostverhoog With your knowledge of the feature, do you have a suggestion on how to reword in a way that makes more sense to the user? Then, we can add the note from aboout how to resolve the problem with a soft delete.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated. Have a look now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants