Timeline for Combination of two fields as a unique key in all_subscriber list
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2020 at 11:20 | vote | accept | Shrijeet Khonde | ||
| Feb 11, 2020 at 11:20 | |||||
| Feb 6, 2020 at 14:34 | answer | added | SDE_Moustache | timeline score: -3 | |
| Feb 6, 2020 at 12:27 | comment | added | Johannes Schapdick | The question is WHY do you want to have this unique contraint of 2 fields instead of the primary key. What is the reasoning behind it. What do you want to ACHIEVE with it. As Lukas told -> Focus on the use case and the problem ... not a scenario you want to achieve, where we do not know what you want to achieve. Btw. like lukas said, you cannot change the allsubscriber to a two field unique constraint so we have to come up with a workaround. Please include the use case | |
| Feb 6, 2020 at 12:12 | history | edited | Shrijeet Khonde | CC BY-SA 4.0 |
added 102 characters in body
|
| Feb 6, 2020 at 11:59 | comment | added | Lukas Lunow | Please update your question to explain what you ultimately are attempting, as I suspect we are dealing with an XY Problem | |
| Feb 6, 2020 at 11:56 | comment | added | Shrijeet Khonde | is there any other way to execute this functionality.? | |
| Feb 6, 2020 at 11:55 | comment | added | Lukas Lunow | You can't change the behaviour of All Subscribers - as it will always choose SubscriberKey as primary key. | |
| Feb 6, 2020 at 11:48 | history | asked | Shrijeet Khonde | CC BY-SA 4.0 |