Proper way to make Contract-Order, force 1-1 relationship
up vote
4
down vote
favorite
I'm looking out for a way to make the relationship between Order and Contract, 1-1, The relationship between both, is optional, but still, I'm unsure if I need to add a custom field to Contract that points to the corresponding order, of if there is a way to declarative restrict the relation, and also allowing for a direct query without the nested sub query in SOQL.
Any Idea?
soql relationships order contracts
asked Dec 12 at 19:49
ekiim
889
add a comment |
up vote
4
down vote
favorite
I'm looking out for a way to make the relationship between Order and Contract, 1-1, The relationship between both, is optional, but still, I'm unsure if I need to add a custom field to Contract that points to the corresponding order, of if there is a way to declarative restrict the relation, and also allowing for a direct query without the nested sub query in SOQL.
Any Idea?
soql relationships order contracts
asked Dec 12 at 19:49
ekiim
889
add a comment |
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I'm looking out for a way to make the relationship between Order and Contract, 1-1, The relationship between both, is optional, but still, I'm unsure if I need to add a custom field to Contract that points to the corresponding order, of if there is a way to declarative restrict the relation, and also allowing for a direct query without the nested sub query in SOQL.
Any Idea?
soql relationships order contracts
asked Dec 12 at 19:49
ekiim
889
I'm looking out for a way to make the relationship between Order and Contract, 1-1, The relationship between both, is optional, but still, I'm unsure if I need to add a custom field to Contract that points to the corresponding order, of if there is a way to declarative restrict the relation, and also allowing for a direct query without the nested sub query in SOQL.
Any Idea?
soql relationships order contracts
soql relationships order contracts
asked Dec 12 at 19:49
ekiim
889
asked Dec 12 at 19:49
ekiim
889
asked Dec 12 at 19:49
ekiim
889
asked Dec 12 at 19:49
ekiim
889
asked Dec 12 at 19:49
ekiim
889
889
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
Yes, You can do that using standard Salesforce Functionality
- Create a Field on Order Named as Contract_Unqiue__c and make it as unique field.
- Create a WF rule on Order and when the order is created , copy the ContractID to the field Contract_Unique__c
Thats it done.
WHen a new order is created for that contract, it will allow you to save it, and if you try to add another order it throw Unique field constraint exception. Thus this allows you to only have 1-1 Relationship ie 1 contract should have atmost 1 order.
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
That is what I thought, but I wanted to Avoid the Custom Field, I thought there was a way to restrict them to1-1similar to thePersonAccountor something. Thanks
– ekiim
Dec 12 at 20:06
Person Accounts are very special objects and and there isnt away to make it via custom SF
– Pranay Jaiswal
Dec 12 at 20:07
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242369%2fproper-way-to-make-contract-order-force-1-1-relationship%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
Yes, You can do that using standard Salesforce Functionality
- Create a Field on Order Named as Contract_Unqiue__c and make it as unique field.
- Create a WF rule on Order and when the order is created , copy the ContractID to the field Contract_Unique__c
Thats it done.
WHen a new order is created for that contract, it will allow you to save it, and if you try to add another order it throw Unique field constraint exception. Thus this allows you to only have 1-1 Relationship ie 1 contract should have atmost 1 order.
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
That is what I thought, but I wanted to Avoid the Custom Field, I thought there was a way to restrict them to1-1similar to thePersonAccountor something. Thanks
– ekiim
Dec 12 at 20:06
Person Accounts are very special objects and and there isnt away to make it via custom SF
– Pranay Jaiswal
Dec 12 at 20:07
add a comment |
up vote
5
down vote
accepted
Yes, You can do that using standard Salesforce Functionality
- Create a Field on Order Named as Contract_Unqiue__c and make it as unique field.
- Create a WF rule on Order and when the order is created , copy the ContractID to the field Contract_Unique__c
Thats it done.
WHen a new order is created for that contract, it will allow you to save it, and if you try to add another order it throw Unique field constraint exception. Thus this allows you to only have 1-1 Relationship ie 1 contract should have atmost 1 order.
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
That is what I thought, but I wanted to Avoid the Custom Field, I thought there was a way to restrict them to1-1similar to thePersonAccountor something. Thanks
– ekiim
Dec 12 at 20:06
Person Accounts are very special objects and and there isnt away to make it via custom SF
– Pranay Jaiswal
Dec 12 at 20:07
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
Yes, You can do that using standard Salesforce Functionality
- Create a Field on Order Named as Contract_Unqiue__c and make it as unique field.
- Create a WF rule on Order and when the order is created , copy the ContractID to the field Contract_Unique__c
Thats it done.
WHen a new order is created for that contract, it will allow you to save it, and if you try to add another order it throw Unique field constraint exception. Thus this allows you to only have 1-1 Relationship ie 1 contract should have atmost 1 order.
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
Yes, You can do that using standard Salesforce Functionality
- Create a Field on Order Named as Contract_Unqiue__c and make it as unique field.
- Create a WF rule on Order and when the order is created , copy the ContractID to the field Contract_Unique__c
Thats it done.
WHen a new order is created for that contract, it will allow you to save it, and if you try to add another order it throw Unique field constraint exception. Thus this allows you to only have 1-1 Relationship ie 1 contract should have atmost 1 order.
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
answered Dec 12 at 19:58
Pranay Jaiswal
13k32351
13k32351
That is what I thought, but I wanted to Avoid the Custom Field, I thought there was a way to restrict them to1-1similar to thePersonAccountor something. Thanks
– ekiim
Dec 12 at 20:06
Person Accounts are very special objects and and there isnt away to make it via custom SF
– Pranay Jaiswal
Dec 12 at 20:07
add a comment |
That is what I thought, but I wanted to Avoid the Custom Field, I thought there was a way to restrict them to1-1similar to thePersonAccountor something. Thanks
– ekiim
Dec 12 at 20:06
Person Accounts are very special objects and and there isnt away to make it via custom SF
– Pranay Jaiswal
Dec 12 at 20:07
That is what I thought, but I wanted to Avoid the Custom Field, I thought there was a way to restrict them to
1-1 similar to the PersonAccount or something. Thanks– ekiim
Dec 12 at 20:06
That is what I thought, but I wanted to Avoid the Custom Field, I thought there was a way to restrict them to
1-1 similar to the PersonAccount or something. Thanks– ekiim
Dec 12 at 20:06
Person Accounts are very special objects and and there isnt away to make it via custom SF
– Pranay Jaiswal
Dec 12 at 20:07
Person Accounts are very special objects and and there isnt away to make it via custom SF
– Pranay Jaiswal
Dec 12 at 20:07
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242369%2fproper-way-to-make-contract-order-force-1-1-relationship%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
