Imagine a scenario where with each Opportunity there's the possibility for sales of multiple related financial products (e.g. mortgage, insurance) in addition to the main product (e.g. home sale).

An Opportunity is a potential property sale.  So for each Opportunity record there's the possibility of one home sale, one insurance sale, one mortgage sale.  

Selling these ancillary products is new so we currently we track the potential revenue related to the home sale directly on the Opportunity Object. 
 
We agree that all these ancillary products cannot be put directly on Opportunity object but we've yet to develop consensus regarding where they belong: the standard Products object or custom objects. 

Those in favor of the Product object say that approach is best because it makes aggregating all the revenue from the related product opportunities easily roll up to the Opportunity object.

Those in favor of the Custom objects wonder if the Products object can handle the complex needs of the business operations.  The examples in Trailhead use Generators for the sample products.  Another official Salesforce example (https://www.youtube.com/watch?v=6_htO6Ju0gU) of Product object in use shows furniture being sold. 

But insurance and mortgages are very different than physical products.  There are no Price Books for insurance or mortgages.  Each client gets a custom quote from a third party.  And the quantity for each product is always one.  So it doesn't seem to be the textbook use case for Products and, if we did use it, it wouldn't look like the Salesforce examples.

Also, getting isurance or mortgage quotes are complex processes that involve humans performing various tasks at various stages of the insurane and mortgage product sales processes.  But Path isn't available on Product which makes our users nervous beause they're familiar with Path and have asked for it.   

Has anyone run into this question before?  Any ideas on how to begin architecting a solution?

Recently I enabled Multi Currency in my org.  Now it’s causing some packaging errors that I don’t know how to address.

The error in question is “In field: field - no CustomField named OBJECT.CurrencyIsoCode found” where OBJECT = name of the object in question (I get these errors on many object).

I get these errors when I (1) mdapi retrieve from main org and then (2) mdapi deploy to a scratch org.

One easy way to get rid of the errors is to remove the Currency field from the Page Layout.
 
I’ve tested this with a few objects and it works BUT (1) I want the Currency field on some object and (2) for some objects (e.g. Contract and Event) this is a required field so I think removing it from the Page Layout would cause other problems.

Any advice on how to deal with this issue?  

I’m attempting to migrate metadata from one org to another using a package.  But my deployment keeps failing with “Error  test/applications/Underwriting.app  Underwriting  invalid cross reference id”

Originally I was all three .app files in my metadata package were failing.  Then I did something (IDK what – I tried a bunch of stuff) that got two of the .app files to deploy and only one is failing now.

Looking at what changed in the .app files that failed but now deploy without error, I notice they no longer contain references to many standard profiles.  They only reference custom profiles and the Admin profile.  No other standard profiles besides Admin.

Also, if I look at the .app files that continues to cause problems, I see that it contains references to many if not all of the standard profiles.  As a result, I suspect it is the inclusion of these standard profiles that is causing problems.

I thought the fix would be easy: go to Setup > App Manager > App Settings > User Profiles, move the standard profiles from the Selected Profiles column to the Available profiles column and then update the package.

The problem is that it does not seem that changes I make to App Manager > App Settings > User Profiles are reflected in the .app metadata files in my package.

Removing standard profiles from the app with the .app file producing the error does not remove them from the .app metadata file.  Similarly, adding standard profiles to the apps whose .app files do not contain standard profiles does not add the selected standard profiles to these .app files.

This has left me perplexed.  Is the issue the standard profiles in the .app file?  If not App Manager > App Settings > User Profiles, how do I control which profiles appear in my .app files? 

Note: I’ve searched for similar errors / possible solutions.  The first link below sounds most similar but it’s marked as a “fixed” known issue as of a year ago so I don’t think that’s the issue.  The second link says there’s an invalid record ID in my code.  But the error messages I get identify the files producing the error and I’m 100% positive they do not contain any record (or other IDs).

https://success.salesforce.com/issues_view?id=a1p3A000000mCIdQAM&title=invalid-cross-reference-id-deploying-custom-app-with-profileactionoverrides-referencing-new-profiles-in-same-deployment (https://success.salesforce.com/issues_view?id=a1p3A000000mCIdQAM&title=invalid-cross-reference-id-deploying-custom-app-with-profileactionoverrides-referencing-new-profiles-in-same-deployment" style="color:blue; text-decoration:underline)

https://developer.salesforce.com/forums/?id=906F0000000BIhXIAW (https://developer.salesforce.com/forums/?id=906F0000000BIhXIAW" style="color:blue; text-decoration:underline)
 

I'm trying to deploy a package to a scratch org via the SFDX CLI using the sfdx force:mdapi:deploy command. 

See screenshot below for exact error message.

I have a "Reinsurer" picklist value on the Account object's Type field that I believe is causing the error.

I've done some research and found two others with a similar error:  
(1) was a version conflict issue and changing the version in package.xml fixed this.  My package.xml shows version 46.0.  Would changing my version fix this?  If so, what version should I use?
(2) Suggestion was to "include same picklist in change set while deployment".  I'm not using change sets.  But maybe the picklist is a package component I didn't add?  I double checked and couldn't find any missing componenets but maybe I missed it?

Also, I don't even use the Account object's Type field.  So if there's a way to ignore or exclude this field from the package and that's easier then that works too.




Bonus: I think the app invalid cross reference error might be related to this issue (https://success.salesforce.com/issues_view?id=a1p3A000000mCIdQAM&title=invalid-cross-reference-id-deploying-custom-app-with-profileactionoverrides-referencing-new-profiles-in-same-deployment) but not sure.  Ant insights regarding that issue would be appreciated

I'm working on the SFDX: Get Ready to Create an App Trailhead module
https://trailhead.salesforce.com/content/learn/modules/sfdx_app_dev/sfdx_app_dev_create_app

It's just copying commands from Trailhead and pasting them into the command prompt.  

Everything was going fine until I got to the "Create Sample Data" section.  I copy and paste the first command from that section into my command prmopt and get an "Unexpected Arguments Error"

Here's a screenshot: https://imgur.com/a/dcNOIk9

Any help would be appreciated.  Thanks!

I’m building an OEM app.  App looks good in Development Org and a Test Org created from the Development Org managed package.

Now I want to move it to a “Golden Package Org” as discussed in this Trailhead module:  https://trailhead.salesforce.com/en/content/learn/modules/isv_app_development/isv_app_development_landscape (https://trailhead.salesforce.com/en/content/learn/modules/isv_app_development/isv_app_development_landscape" style="color:blue; text-decoration:underline)

I created a package.xml file using this tool: https://packagebuilder.herokuapp.com/ (https://packagebuilder.herokuapp.com/" style="color:blue; text-decoration:underline)

Then I used the package.xml file and the ANT Migration tool’s retrieveUnpackaged command to download metadata locally.  That worked.

Then I ran the deployUnpackaged command, got hundreds of errors, and the deployment failed.

Here’s a link to my error log: https://drive.google.com/file/d/1W7VdLK5xDCvDuTLyQgBJrlacik4iao7h/view?usp=sharing (https://drive.google.com/file/d/1W7VdLK5xDCvDuTLyQgBJrlacik4iao7h/view?usp=sharing" style="color:blue; text-decoration:underline)

Can anyone let me know where I’m going wrong? 

And/or if there's an easier way than ANT to get changes from my Development Org to a Golden Package Org?  I could create the release managed package from the Development Org but I had a different namespace prefix in mind for the finished product and would rather keep Development and Packaging orgs separate.

Thanks in advance!
 

I‘ve created a managed package that includes objects with Lightning Record Pages (LRP).

When I attempt to install the managed package in a test environment, I get the error “Small is not a supported form factor" which causes my install to fail.

I’ve traced this error back to the LRP activation.

If I activate a LRP as an Org Default I’m given the option to make it the default for Desktop, Phone, or Desktop and Phone.

I chose Desktop and Phone because why wouldn’t I want users to have a good mobile experience. 

But the Phone / mobile option caused the error.  I verified this by changing the activation to Desktop only and the install worked. 

Interestingly, if I go down the “App, Record Type, and Profile” activation path (some of my objects have different record types with different LRPs) I don’t get an option to choose Phone.  Desktop is the only option.

So, is there a way to activate LRPs for Phone without causing errors? 

If not, any idea why Salesforce give the option of assigning an LRP as the Phone view?   

I'm working on an OEM solution.  I have created Dev and Test enviroments via Environment Hub.  I will probably create a couple more Dev and Test environments as I progress.

I've begun to build a custom - my solution has many custom objects - sample dataset that I'd like to be able to easily import into my various environments.

Just uploaded my first object from my custom data set and realized I don't know how I'm going to handle the relationships.

My concern is that I won't be able to keep record IDs consistent across environments and therefore I won't be able to programatically establish relationships.

Any suggestions on how to best address this?

Working on Windows 10.  

I've installed Zulu 11.  Proof:



I've installed Dataloader 45.0.0

I open Data Loader using the shortcut created during installation.

This screen flashes for a second then disappears:



And then nothing happens... no Data Loader.

I've tried reinstalling and restarting but that doesn't help.

Any ideas?

I’m attempting to migrate metadata from one org to another using a package.  But my deployment keeps failing with “Error  test/applications/Underwriting.app  Underwriting  invalid cross reference id”

Originally I was all three .app files in my metadata package were failing.  Then I did something (IDK what – I tried a bunch of stuff) that got two of the .app files to deploy and only one is failing now.

Looking at what changed in the .app files that failed but now deploy without error, I notice they no longer contain references to many standard profiles.  They only reference custom profiles and the Admin profile.  No other standard profiles besides Admin.

Also, if I look at the .app files that continues to cause problems, I see that it contains references to many if not all of the standard profiles.  As a result, I suspect it is the inclusion of these standard profiles that is causing problems.

I thought the fix would be easy: go to Setup > App Manager > App Settings > User Profiles, move the standard profiles from the Selected Profiles column to the Available profiles column and then update the package.

The problem is that it does not seem that changes I make to App Manager > App Settings > User Profiles are reflected in the .app metadata files in my package.

Removing standard profiles from the app with the .app file producing the error does not remove them from the .app metadata file.  Similarly, adding standard profiles to the apps whose .app files do not contain standard profiles does not add the selected standard profiles to these .app files.

This has left me perplexed.  Is the issue the standard profiles in the .app file?  If not App Manager > App Settings > User Profiles, how do I control which profiles appear in my .app files? 

Note: I’ve searched for similar errors / possible solutions.  The first link below sounds most similar but it’s marked as a “fixed” known issue as of a year ago so I don’t think that’s the issue.  The second link says there’s an invalid record ID in my code.  But the error messages I get identify the files producing the error and I’m 100% positive they do not contain any record (or other IDs).

https://success.salesforce.com/issues_view?id=a1p3A000000mCIdQAM&title=invalid-cross-reference-id-deploying-custom-app-with-profileactionoverrides-referencing-new-profiles-in-same-deployment (https://success.salesforce.com/issues_view?id=a1p3A000000mCIdQAM&title=invalid-cross-reference-id-deploying-custom-app-with-profileactionoverrides-referencing-new-profiles-in-same-deployment" style="color:blue; text-decoration:underline)

https://developer.salesforce.com/forums/?id=906F0000000BIhXIAW (https://developer.salesforce.com/forums/?id=906F0000000BIhXIAW" style="color:blue; text-decoration:underline)
 

I‘ve created a managed package that includes objects with Lightning Record Pages (LRP).

When I attempt to install the managed package in a test environment, I get the error “Small is not a supported form factor" which causes my install to fail.

I’ve traced this error back to the LRP activation.

If I activate a LRP as an Org Default I’m given the option to make it the default for Desktop, Phone, or Desktop and Phone.

I chose Desktop and Phone because why wouldn’t I want users to have a good mobile experience. 

But the Phone / mobile option caused the error.  I verified this by changing the activation to Desktop only and the install worked. 

Interestingly, if I go down the “App, Record Type, and Profile” activation path (some of my objects have different record types with different LRPs) I don’t get an option to choose Phone.  Desktop is the only option.

So, is there a way to activate LRPs for Phone without causing errors? 

If not, any idea why Salesforce give the option of assigning an LRP as the Phone view?   

Working on Windows 10.  

I've installed Zulu 11.  Proof:



I've installed Dataloader 45.0.0

I open Data Loader using the shortcut created during installation.

This screen flashes for a second then disappears:



And then nothing happens... no Data Loader.

I've tried reinstalling and restarting but that doesn't help.

Any ideas?

I'm working on the SFDX: Get Ready to Create an App Trailhead module
https://trailhead.salesforce.com/content/learn/modules/sfdx_app_dev/sfdx_app_dev_create_app

It's just copying commands from Trailhead and pasting them into the command prompt.  

Everything was going fine until I got to the "Create Sample Data" section.  I copy and paste the first command from that section into my command prmopt and get an "Unexpected Arguments Error"

Here's a screenshot: https://imgur.com/a/dcNOIk9

Any help would be appreciated.  Thanks!

I’m building an OEM app.  App looks good in Development Org and a Test Org created from the Development Org managed package.

Now I want to move it to a “Golden Package Org” as discussed in this Trailhead module:  https://trailhead.salesforce.com/en/content/learn/modules/isv_app_development/isv_app_development_landscape (https://trailhead.salesforce.com/en/content/learn/modules/isv_app_development/isv_app_development_landscape" style="color:blue; text-decoration:underline)

I created a package.xml file using this tool: https://packagebuilder.herokuapp.com/ (https://packagebuilder.herokuapp.com/" style="color:blue; text-decoration:underline)

Then I used the package.xml file and the ANT Migration tool’s retrieveUnpackaged command to download metadata locally.  That worked.

Then I ran the deployUnpackaged command, got hundreds of errors, and the deployment failed.

Here’s a link to my error log: https://drive.google.com/file/d/1W7VdLK5xDCvDuTLyQgBJrlacik4iao7h/view?usp=sharing (https://drive.google.com/file/d/1W7VdLK5xDCvDuTLyQgBJrlacik4iao7h/view?usp=sharing" style="color:blue; text-decoration:underline)

Can anyone let me know where I’m going wrong? 

And/or if there's an easier way than ANT to get changes from my Development Org to a Golden Package Org?  I could create the release managed package from the Development Org but I had a different namespace prefix in mind for the finished product and would rather keep Development and Packaging orgs separate.

Thanks in advance!
 

I'm working on an OEM solution.  I have created Dev and Test enviroments via Environment Hub.  I will probably create a couple more Dev and Test environments as I progress.

I've begun to build a custom - my solution has many custom objects - sample dataset that I'd like to be able to easily import into my various environments.

Just uploaded my first object from my custom data set and realized I don't know how I'm going to handle the relationships.

My concern is that I won't be able to keep record IDs consistent across environments and therefore I won't be able to programatically establish relationships.

Any suggestions on how to best address this?

Working on Windows 10.  

I've installed Zulu 11.  Proof:



I've installed Dataloader 45.0.0

I open Data Loader using the shortcut created during installation.

This screen flashes for a second then disappears:



And then nothing happens... no Data Loader.

I've tried reinstalling and restarting but that doesn't help.

Any ideas?