How to unit test with OpportunityLineItemSchedule objects?
I wrote a OpportunityLineItem trigger that works with the OpportunityLineItemSchedule items related to it. Now I want to write unit tests for this trigger, and want to use sfdx to push the code to a scratch org to test things.
However, sfdx force:source:push
fails on this (simplified) code:
@isTest
private class OpportunityLineItemTest {
@isTest static void test() {
OpportunityLineItemSchedule schedule = new OpportunityLineItemSchedule();
}
}
with the error:
Invalid type: OpportunityLineItemSchedule
How do I create a unit test for OpportunityLineItem objects that use OpportunityLineItemSchedule objects? Do I need to enable a certain feature in the project-scratch-def.json
to be able to use these objects?
unit-test salesforcedx
add a comment |
I wrote a OpportunityLineItem trigger that works with the OpportunityLineItemSchedule items related to it. Now I want to write unit tests for this trigger, and want to use sfdx to push the code to a scratch org to test things.
However, sfdx force:source:push
fails on this (simplified) code:
@isTest
private class OpportunityLineItemTest {
@isTest static void test() {
OpportunityLineItemSchedule schedule = new OpportunityLineItemSchedule();
}
}
with the error:
Invalid type: OpportunityLineItemSchedule
How do I create a unit test for OpportunityLineItem objects that use OpportunityLineItemSchedule objects? Do I need to enable a certain feature in the project-scratch-def.json
to be able to use these objects?
unit-test salesforcedx
add a comment |
I wrote a OpportunityLineItem trigger that works with the OpportunityLineItemSchedule items related to it. Now I want to write unit tests for this trigger, and want to use sfdx to push the code to a scratch org to test things.
However, sfdx force:source:push
fails on this (simplified) code:
@isTest
private class OpportunityLineItemTest {
@isTest static void test() {
OpportunityLineItemSchedule schedule = new OpportunityLineItemSchedule();
}
}
with the error:
Invalid type: OpportunityLineItemSchedule
How do I create a unit test for OpportunityLineItem objects that use OpportunityLineItemSchedule objects? Do I need to enable a certain feature in the project-scratch-def.json
to be able to use these objects?
unit-test salesforcedx
I wrote a OpportunityLineItem trigger that works with the OpportunityLineItemSchedule items related to it. Now I want to write unit tests for this trigger, and want to use sfdx to push the code to a scratch org to test things.
However, sfdx force:source:push
fails on this (simplified) code:
@isTest
private class OpportunityLineItemTest {
@isTest static void test() {
OpportunityLineItemSchedule schedule = new OpportunityLineItemSchedule();
}
}
with the error:
Invalid type: OpportunityLineItemSchedule
How do I create a unit test for OpportunityLineItem objects that use OpportunityLineItemSchedule objects? Do I need to enable a certain feature in the project-scratch-def.json
to be able to use these objects?
unit-test salesforcedx
unit-test salesforcedx
asked Nov 18 at 21:03
Patrick Atoon
1965
1965
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You have to enable a Product schedule feature in the project-scratch-def.json
, e.g. like this:
{
"country": "US",
"edition": "Developer",
"features": ,
"orgPreferences": {
"enabled": [
"S1DesktopEnabled",
"IsRevenueScheduleEnabled"
],
"disabled":
},
"orgName": "My Org",
"adminEmail": "admin@my.org"
}
Once you create the scratch org with IsRevenueScheduleEnabled
enabled, the type OpportunityLineItemSchedule
will be available in unit tests.
My bad, i thought OpportunityLineItemSchedule is triggername
– Pranay Jaiswal
Nov 18 at 21:31
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%2f239772%2fhow-to-unit-test-with-opportunitylineitemschedule-objects%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
You have to enable a Product schedule feature in the project-scratch-def.json
, e.g. like this:
{
"country": "US",
"edition": "Developer",
"features": ,
"orgPreferences": {
"enabled": [
"S1DesktopEnabled",
"IsRevenueScheduleEnabled"
],
"disabled":
},
"orgName": "My Org",
"adminEmail": "admin@my.org"
}
Once you create the scratch org with IsRevenueScheduleEnabled
enabled, the type OpportunityLineItemSchedule
will be available in unit tests.
My bad, i thought OpportunityLineItemSchedule is triggername
– Pranay Jaiswal
Nov 18 at 21:31
add a comment |
You have to enable a Product schedule feature in the project-scratch-def.json
, e.g. like this:
{
"country": "US",
"edition": "Developer",
"features": ,
"orgPreferences": {
"enabled": [
"S1DesktopEnabled",
"IsRevenueScheduleEnabled"
],
"disabled":
},
"orgName": "My Org",
"adminEmail": "admin@my.org"
}
Once you create the scratch org with IsRevenueScheduleEnabled
enabled, the type OpportunityLineItemSchedule
will be available in unit tests.
My bad, i thought OpportunityLineItemSchedule is triggername
– Pranay Jaiswal
Nov 18 at 21:31
add a comment |
You have to enable a Product schedule feature in the project-scratch-def.json
, e.g. like this:
{
"country": "US",
"edition": "Developer",
"features": ,
"orgPreferences": {
"enabled": [
"S1DesktopEnabled",
"IsRevenueScheduleEnabled"
],
"disabled":
},
"orgName": "My Org",
"adminEmail": "admin@my.org"
}
Once you create the scratch org with IsRevenueScheduleEnabled
enabled, the type OpportunityLineItemSchedule
will be available in unit tests.
You have to enable a Product schedule feature in the project-scratch-def.json
, e.g. like this:
{
"country": "US",
"edition": "Developer",
"features": ,
"orgPreferences": {
"enabled": [
"S1DesktopEnabled",
"IsRevenueScheduleEnabled"
],
"disabled":
},
"orgName": "My Org",
"adminEmail": "admin@my.org"
}
Once you create the scratch org with IsRevenueScheduleEnabled
enabled, the type OpportunityLineItemSchedule
will be available in unit tests.
answered Nov 18 at 21:28
Patrick Atoon
1965
1965
My bad, i thought OpportunityLineItemSchedule is triggername
– Pranay Jaiswal
Nov 18 at 21:31
add a comment |
My bad, i thought OpportunityLineItemSchedule is triggername
– Pranay Jaiswal
Nov 18 at 21:31
My bad, i thought OpportunityLineItemSchedule is triggername
– Pranay Jaiswal
Nov 18 at 21:31
My bad, i thought OpportunityLineItemSchedule is triggername
– Pranay Jaiswal
Nov 18 at 21:31
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%2f239772%2fhow-to-unit-test-with-opportunitylineitemschedule-objects%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