Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
As our investigation into products continues, along with the inability to re-parent a product, another action which is apparently impossible (at least according to the second part of this blog article but not the diagram at the top of the article), is reactivating a retired product.
We have attempted to use an on-demand workflow to change the status to Active, Draft and Under Revision but are greeted with an error message saying that a retired product cannot be changed.
In my opinion, a software package should never, ever be able to prevent an administrator from changing the status of a record. My assumption is that the implementation of the retire function is such that allowing a change of status sufficiently breaks the system in a catastrophic way and is therefore, simply wrong.
This post is partially a vent and partially a warning to others:
Never, ever, ever retire a product unless you are so damn sure that you will never under any conceivable circumstance want to re-activate it. For gods sake if you really do retire a product, change the product ID before you do because unless you disable de-duplication, you will never, ever, ever be able to use the product ID again. And yes Microsoft, sometimes product IDs, rightly or wrongly, are re-used.
Please, someone - I really hope we are wrong and that products can be un-retired.
Unfortunately, for products that have dynamic product properties, you will receive the message ""You can't set a retired property to an active state." if you try and re-activate after retiring. If the product is not part of a product family with no product properties you can 'Activate' again after retiring.
The work around is to clone the product and give a different product number - or as you say always change the product ID before retiring.
Again - sorry for the answer that you didn't want!
You can post your suggestions to connect.microsoft.com
Thank-you for replying Scott!
Microsoft have informed us that this is a bug and that we should be able to reactivate a retired product. Apparently they are working on a fix... we shall see!
Hey emj -- Have they updated you on whether or not this was fixed in the new update rollup? I cannot seem to delete a Product Bundle or even "un-retire" it in order to modify the associations with other entities.
Dynamics CRM Application till now has no way to revert the status of a Product Family or a Product (that has a parent) from Retired to Active/Draft.
Unfortunately at on operational environment, a product family was set to retired by mistake and it was cascaded to all the subordinated products. Since there is no embedded way at the Application,the last solution is to update it at the DB.
You can change the status of the product by placing an update query on the database. Here is the query.
update Product set StateCode = 2, StatusCode = 0
where (StateCode = 1 AND StatusCode = 2)
Hint: Retired StateCode=1 , StatusCode =2
Draft StateCode=2 , StatusCode =0
Thank You, It Worked!
Is there any way to update the statecode and statuscode on an online installation?
Anyone facing this issue should log help desk tickets. It is only by constant user "feedback" that this inane limitation will be removed.
14 months on and the "bug" still persists!
Can confirm... its still an issue in V8.2 and V9.
I found this in Ideas.dynamics.com, please upvote!
Also upvote idea.dynamics.com! ideas.dynamics.com/.../1917081
Looks like this is still an issue 3 years on, come on Microsoft get this fixed!!!!
You can export the record, modify the ID and then re-import. This will then allow you retain your numbering if you forgot to update the ID prior to retiring the product
Business Applications communities