• Ron Maffrand
  • NEWBIE
  • 10 Points
  • Member since 2014

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 2
    Replies
We have an API user with system administator profile that we wish to have cloned to a custom profile with everything the same except the password does not expire.

Is this a bad practice? Reason, we have SOA processes that are failing when the password is set to expire. Need to ensure the dependent processes are not affected by enforced password policy.
How do I prevent the final Solution record in a list of solution records from deleting for the parent Opportunity record?
Steps suggested by a developer as follows:
>>create a trigger on Solution Record object on before delete event
>>Fetch the details of the parent opportunity record using the id of the solution record
>>check the number of solution record associated wit the opportunity.
>>if the result is one it means that this solution record is the last record and display an error message.
>>if the result is more than one allow to delete the record.

Anybody have sample code to do this or similar example?

We have an API user with system administator profile that we wish to have cloned to a custom profile with everything the same except the password does not expire.

Is this a bad practice? Reason, we have SOA processes that are failing when the password is set to expire. Need to ensure the dependent processes are not affected by enforced password policy.