I'm just wondering how to remove the customer need (LeadType) on the opportunity mini-page. The problem is that this customer need field is getting dynamically set with a method on a third-party module. With that being said I can not edit the module and take out the code where it is being set. It is part of the CoreLeadOpportunity package. It is getting set in this code.

			addQueryColumns: function(insertQuery) {
				this.addLookupQueryColumn(insertQuery, {
					columnName: "Account",
					entityColumnName: "QualifiedAccount"
				});
				this.addLookupQueryColumn(insertQuery, {
					columnName: "Contact",
					entityColumnName: "QualifiedContact"
				});
				this.addLookupQueryColumn(insertQuery, {
					columnName: "LeadType",
					entityColumnName: "LeadType"
				});

Any help would be appreciated. Thanks!

Like 0

Like

1 comments

Please create a replacing client module for the OpportunityMiniPage schema. Then remove the fields which aren't needed in the diff block in the newly created replacing client module. Please feel free to use the example below. Note that the isRequired property of the LeadType attribute must be set to false.

define("OpportunityMiniPage", [],

        function() {

    return {

        entitySchemaName: "Opportunity",

        mixins: {

        },

        attributes: {

            "LeadType": {"isRequired": false}

        },

        methods: {

        

        },

        diff: /**SCHEMA_DIFF*/[

            {

                "operation": "remove",

                "name": "LeadType"

            },

            

        ]/**SCHEMA_DIFF*/

    };

});

 

Show all comments

Hi,

 

When I export a package, does it also include the section cases?

 

I have created a package, set it as current and then I made a few section cases. I can not see anything in the package. Will the section cases be there in the package when I export the packages to other instance?

 

If not, how should I approach this?

 

Thanks in advance.

 

Regards,

AK

Like 0

Like

1 comments

Hello!

Section cases are added to the package as a regular configuration object, looks relatively similar to business process (e.g. http://prntscr.com/nqret9) When you add a case while you have current package set to your package the case would be saved in your package. You should see created cases in your package though, please check your current package setting and dependencies of your package. 

Best regards,

Dennis

Show all comments

Transferred the package from one instance to another instance. The transfer was successful.

In the system setting the current package is also set as the transferred package. 

But any changes made is getting reflected in the default custom package rather than the new transferred package. 

The whole thing is happening in our dev cloud environment so even though the edit settings for the imported package has been set to "Allow", the package still restricts to edit and all the changes to the objects and schema are residing in "Custom" package.

Please suggest a efficient way on managing the changes relevant to that package. Kindly help us resolving it.

 

Thanks

Saranya

Like 0

Like

1 comments

Dear Saraya, 

Please make sure that the package you've set as a current package is not locked and the current package system setting is set to your package. If the package is locked the system would set Custom as a current package as it can't save anything to the locked package. If your package is unlocked and the current package is set to your package please contact support team at support@bpmonline.com

Best regards, 

Dennis

Show all comments