Closed kevinmatos closed 6 years ago
Hi, that sounds really unpleasant... :-/ It sounds like something failed and left the attribute in some limbo state. During tests I have removed numbering both by clearing the number format and updating the attribute, and by deleting the attribute entirely. This worked. (to clear the number you must however check the "Don't require SEQNUM" checkbox, otherwise an exception is shown, this is a bug)
Was the attribute in question a new attribute that you created using ANM, or was it an existing attribute?
Hello Jonas,
Thank you for the prompt response.
I tried clearing the number format and updating the attribute, but that is where I got the exception error. I also just tried it again with the “Don’t require SEQNUM” checkbox selected and it seemed to work with no errors. But when the ANM reloads the field in question still appears as an auto numbering attribute, and I continue to have the same issues as stated in my email.
The attribute was an existing one created in CRM and not with the ANM. I wasn’t able to delete it either through the ANM or CRM, as it has 18 dependencies. The remaining dependencies are system views that I cannot re-create, which I now cannot edit or remove the field in question as the views show with no fields in them (see screenshot below).
Please let me know if there is a step I am missing in this process of removing the field as an auto number attribute or another way I can troubleshoot this issue.
Thank you,
Kevin Matos Senior Consultant: Customer Engagement Karabina ™
You did it the right way, what CRM did we can only guess... You could try deleting the attribute using XrmToolBox plugin Attribute Manager.
Hello Jonas,
Thank you for the recommendation. Between the Attribute Manager and View Designer plugins on XrmToolBox, I was able to remove all the view dependencies and delete the attribute. Now all the views designer in CRM shows the fields as it did originally, so problem solved!
Thank you again for your prompt assistance.
Just a suggestion: I hope that in the future you can consider incorporating a way to populate the auto numbering to an attribute on trigger of a workflow or based on a condition, rather than just on create of the record.
Regards,
Kevin Matos Senior Consultant: Customer Engagement Karabina ™
Glad to hear it got solved!
That is a good suggestion, which is probably possible in many third party solutions for auto numbering. ANM however is merely a UI to the built in CRM functionality for auto numbers, and for this it is not possible to do so. You can read more about the functionality here: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/create-auto-number-attributes I also suggest that you submit an idea at http://crmideas.dynamics.com for the features you would like to see from Microsoft!
I am attempting to use the AutoNumber feature. I used the system "name" field which is the primary field for the entity since it is a text field. This has caused all types of trouble were the name field has now disappeared from the entity to add to views and other form related issues. How do I remove the AutoNumber feature on a system field?
Can you verify the version of your CRM instance? I have recently discovered a bug in CRM for auto number attributes, which has been reported to and confirmed by Microsoft.
Hello Jonas, our CRM is online v9. I also noticed that any entities to which I apply the auto-numbering to disappear from the solution, including the default solution. Thank you, Kevin
Get Outlook for iOShttps://aka.ms/o0ukef
From: Jonas Rapp notifications@github.com Sent: Friday, February 23, 2018 10:30:54 PM To: rappen/AutoNumManager Cc: Kevin Matos; Author Subject: Re: [rappen/AutoNumManager] Error when trying to remove Auto Numbering from a field (#6)
Can you verify the version of your CRM instance? I have recently discovered a bug in CRM for auto number attributes, which has been reported to and confirmed by Microsoft.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/rappen/AutoNumManager/issues/6#issuecomment-368130202, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ai9hm9XHd6-8iVi5gAIzT6anv-VQH6hLks5tXx_7gaJpZM4SLnSi.
Sounds like it is related to the problem I have seen in version 9.0.1.x. Another symptom has been that views containing auto number attributes cannot be customized anymore. Let's just cross our fingers that MS provides a fix soon.
Hey Kevin, I am encountering the same problem. The entity has disappeared in the solution and default solution but if you create a new solution, you can see it and add it to the new solution. Unfortunately, the solution component disappears again within the solution.
I did a comparison with the custo9mization.xml and found the "DisplayMask" tag is updated and I believe this is why the entity disappears. I too have a pending ticket with Microsoft on this.
Sorry to hear that @rasotoipc, and thanks for your investigation. Is your ticket with MS public so we can all track any progress there?
Hi Jonas, I too am seeing some of the issues stated above. Once I configure a field for auto number I noticed it's set to 'not searchable', and this cannot be changed. Also the field cannot be added to any forms or views as it just doesn't appear in the list of available fields. I created a new attribute and added it the Active Contacts view before configuring the field for auto number. When I return to the view editor the autonumber column does not appear and neither do any columns to the right of it, but I can see them in the published view. Back to the editor, clicking add columns does nothing and as I cannot see the autonumber column I cannot remove it, but the dependency is there looking at the field. I tried removing the autonumber configuration using Auto Number Manager but I got an error that it was expecting a {SEQNUM;n} value, as a last resort I deleted the attribute using Attribute Manager. I've experienced all these issues in 9.0.1 also.
@AdamGray77 I can only say that I feel your pain. This is a Microsoft issue that we are all hoping to be resolved as soon as possible. I am trying to track with MS to get info about the progress.
@kevinmatos @rasotoipc @AdamGray77
I just got confirmed that the problem is identified and the fix is planned for release in end of April 2018. The date is not fixed, if we are lucky it could be released earlier than that :)
Hello Jonas,
Thank you very much for the feedback and updates. Glad to hear that a fix will be applied with the next release.
Regards,
Kevin Matos Senior Consultant: Customer Engagement Karabina ™
Hi @rappen ,
Do you have a reference id for the issue that has been confirmed by Microsoft? I also have a ticket open with their support for the same issue.
Thanks, Damian
I ran into the same problem many of you described. I'm working in a v9 sandbox and added an auto-number definition to the default name field on a custom entity. After doing that, the entity no longer appears in any solution (even the default solution), thus it's not possible to make further changes to the entity without navigating to the entity info/edit page directly. Even with that, the name field is locked down and it's not possible to edit any views.
After our demo on Monday, we're hoping that we can delete the custom entity and start over with a new one without any problems. Of course, we won't be using the built-in auto-numbering again until Microsoft can confirm that they've fixed (and tested) everything.
@dejmjin Unfortunately I have not been able to get any reference for the MS internal issue.
Thanks @rappen - I'm in contact with both Microsoft Support and FastTrack to try and get a fix for this issue.
I can confirm that there's a release fix for this (9.0.1.621 should have it). However, while that release fix allows for views to be modified, it does not allow for modifying the field (i.e. turn on/off auditing). There is a separate ticket for that (I don't have a public # for it).
Thanks for the update!
Closing this issue now as it appears MS have released a bug fix for it. Feel free to reopen or create a new issue if more problems occur!
Update notes: https://support.microsoft.com/en-us/help/4099130
Thanks....
Hi, I have tried to remove the auto number from the primary attribute but i am getting the same error again.Can you please help See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
** Exception Text ** System.FormatException: Format string must contain a {SEQNUM:n} placeholder. at Rappen.XTB.AutoNumManager.AutoNumMgr.ParseFormatSEQNUM(String format, String seed) at Rappen.XTB.AutoNumManager.AutoNumMgr.WriteAttribute(Boolean update) at Rappen.XTB.AutoNumManager.AutoNumMgr.btnCreateUpdate_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
Hi @ramakanta090 The actuall error message is somewhere at the top: Format string must contain a {SEQNUM:n} placeholder. This is a bug in ANM at the moment, if you check the Don't require SEQNUM checkbox before clicking Delete attribute, you should be good to go.
Thanks a lot...It saves my Day..you are CRM Champion....
Good Day,
I created separate entities to hold my auto-numbering records, and set the auto-numbering attribute as the ‘name’ field for the entity. Shortly after creating the entities, they disappear from my Solution Explorer in both the original solution in which I added the entity, as well as the Default Solution. So I no longer have any way to access this entity from any solution if I want to make changes to the entity.
Please advise.
Thank you,
Hi, I think I have heard that there can be a problem in the platform when you assign auto number format to the primary attribute. My advise would be to raise a ticket with Microsoft, as this is outside the control of ANM.
hi there, are there still issues with the platform and the autonumbering feature or has MS resolved all of them? Do entities still disappear?
@mmartyna I recently added an auto-number to the primary field of a custom entity and everything appears to be working fine. The version of the instance I applied the auto-number to is 9.1.0.643.
is there a way to remove auto-numbering feature from an attribute without deleting the attribute from the system?
Hi @mmartyna Yes you can remove the numbering format without deleting the attribute, see my first comment at the top of this thread: https://github.com/rappen/AutoNumManager/issues/6#issuecomment-367085003
Hello, I set a field as an auto-numbering field and then tried to undo the customization by removing the sequence and updating the field. I received an "Unhandled Exception" error and now every view that the field was referencing has become in-editable and I cannot even remove the field from the system views to remove the dependencies and delete the field. Is there a better way to undo the auto-numbering on a field without error, or fix my views so I can delete the dependencies and the field and try again with a new one? Thank you, Kevin