最近搜索
没有最近搜索

Jason Martens
已加入2021年5月06日
·
最后活动2021年10月16日
关注
0
关注者
0
活动总数
4
投票
0
订阅
1
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Jason Martens
Jason Martens 进行了评论,
Hi Jason, when you create multiple relationships with different PC source IDs, you are creating *different* relationships for each PC. The same is true for one-to-one: each relationship is a separate relationship. The difference between one-to-one and one-to-many is that the target field in the one-to-many relationship type is an array. Whereas the target field in the one-to-one is a single ID.
You should not be able to create multiple relationships with the *same* PC source ID in either the one-to-one or the one-to-many example.
Does that help?
查看评论 · 已于 2021年3月26日 发布 · Jason Martens
0
关注者
0
投票
0
评论
Jason Martens 进行了评论,
Hi Matt, I think you are on the right track, but I'm not sure you need the `location_ticket` object, unless it's holding additional properties about the relationship. You should be able to create a one-to-many relationship between location -> zen:ticket as well as a one-to-many relationship between zen:ticket -> location. Then when you need to associate a ticket to a location, you would create a ticket -> location relationship for the ticket, and a corresponding location -> ticket relationship if you want to know all tickets associated with a location.
查看评论 · 已于 2021年3月26日 发布 · Jason Martens
0
关注者
0
投票
0
评论
Jason Martens 进行了评论,
Hello Matt, to represent many-to-many relationships, you need to create multiple relationship types that go in both directions. Let me know if that doesn't work for you for some reason.
I'm not sure about the Insights question yet, someone will follow up about that.
查看评论 · 已于 2021年3月26日 发布 · Jason Martens
0
关注者
0
投票
0
评论