Browse Source

Fixing issue with 1:N relationships and multiple fields, issue #1753.

pull/4023/head
mike12345567 5 years ago
parent
commit
052d14ad38
  1. 4
      packages/server/src/db/linkedRows/LinkController.js
  2. 1
      packages/worker/src/api/routes/tests/realEmail.spec.js

4
packages/server/src/db/linkedRows/LinkController.js

@ -211,14 +211,14 @@ class LinkController {
// iterate through the link IDs in the row field, see if any don't exist already
for (let linkId of rowField) {
if (linkedSchema.relationshipType === RelationshipTypes.ONE_TO_MANY) {
const links = (
let links = (
await getLinkDocuments({
appId: this._appId,
tableId: field.tableId,
rowId: linkId,
includeDocs: IncludeDocs.EXCLUDE,
})
).filter(link => link.id !== row._id)
).filter(link => link.id !== row._id && link.fieldName === linkedSchema.name)
// The 1 side of 1:N is already related to something else
// You must remove the existing relationship

1
packages/worker/src/api/routes/tests/realEmail.spec.js

@ -53,7 +53,6 @@ describe("/api/admin/email", () => {
it("should be able to send a welcome email", async () => {
await sendRealEmail(EmailTemplatePurpose.WELCOME)
})
it("should be able to send a invitation email", async () => {

Loading…
Cancel
Save