최근 검색
최근 검색 없음

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
댓글