Membership Type Names are user editable and in our experience change from time to time, however any of the Actions that use the MembershipTypeSpecification to populate a Membership Type will save the Name
Membership Type Names are user editable and in our experience change from time to time, however any of the Actions that use the MembershipTypeSpecification to populate a Membership Type will save the Name. This can then cause the Action to fail if the Membership Type Name is changed, since the stored name in the Action no longer matches the Membership Type Name in the system.
It would be more robust to store the Membership Type ID rather than the Membership Type Name. See https://lab.civicrm.org/extensions/action-provider/-/blob/master/Civi/ActionProvider/Action/Membership/Parameter/MembershipTypeSpecification.php#L37
I will be putting up a PR to add a new Parameter specification for MembershipType to allow the storing of Membership Type IDs.
@jaapjansma just a heads up and highlighting a future problem that people are yet to experience.
Agileware Ref: CVAP-58