Fixing issue with 1:N relationships and multiple fields, issue #1753.
This commit is contained in:
parent
1badf70f46
commit
60de9ccb28
|
@ -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
|
||||
|
|
|
@ -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…
Reference in New Issue