We have a project that doesn't have any use of Cha...
# sdf
n
We have a project that doesn't have any use of Charge Based Billing, the customer's SB doesn't have it not does their Production account. When we Deploy to Production (Webstorm) the Manifest gets updated automatically with <feature required="true">CHARGEBASEDBILLING</feature>. The account doesn't have the feature and the deployment stops. I've tried making required=false for this feature but it always gets updated to true prior to deployment and subsequently fails. I did have some objects and consts called custentity_charges and chargeDate which have renamed. What else could be giving the project the look of needing the feature?
a
do you have project instances, or project templates which are set to charge based billing?
and for the record I don't think the SDF deploy process parses your code variables looking for something that sounds like it interacts with certain features. I think it very explicitly looks at script ids in XML and sees actual references
I also don't understand what the automatically adding the feature back means... unless you ASK it to update your manifest using the "add dependencies to manifest" option, nothing but YOU should be modifying the manifest.
if you've automated a build process that includes that step of auto adding dependencies, then I'd suggest disabling that temporarily and trying to deploy with the feature turned off... I'm sure it will still fail but you might get an error message that indicates where the issue is. what happen when you validate rather than deploy? any difference?