Has anybody been noticing when you add a custom control sometimes it will create multiples?
I have on a couple had a couple instances where I add a second textbox and it is also named EpiTextBoxC1.
I can delete one of them, but then the second says cannot delete a native control. If I delete from code and reload I can start over from scratch again.
Unfortunately such is life in the Customization IDE. Sure would be awesome if Epicor would release that code opensource and let us nerds who use it daily to make it awesomesauce.
<Pester> @Bart_Elia </Pester>
You are pestering the wrong guy. Sure I did the original Clientele.Net product V8/E9/E10 took as a starting point but that team took it to many more places than I dreamed of. I’m the wire and server guy. All those rounded rectangles and dancing babies has never been a skillset. My UIs are PowerShell. 
PowerShell, eh? So we don’t have to Pester you because you Pester your scripts?
lol I had not seen that before. I do like the BDD approach to the testing though. Big fan of BDD
Sure would be a great time for a wise guy to buy up that URL and get their RickRoll on haha!
I’ve noticed this also. I think it is often after placing a control, then doing a copy of that control, maybe after editing events. The best way I found to fix the issue is through the XML editor and remove all references to the control(s), delete the controls from the interface (I delete both) then save, quit, re-edit the customization and add the controls back. Bit of a PITA, but seems to work.
On a related note, I also had issues when using the Script editor and viewing All Code (Read Only) which would sometimes end up saving all the code as the customization which, upon editing again, doubled up definitions. To resolve this one, I had to use the Customization Maintenance → Compile/Script Errors-> [Select Issue Helper…] and remove the duplicate code. I haven’t been able to replicate this at will, but happened a couple of times.
@AndrewM Thanks for sharing. I wasn’t even aware of the Customization Maintenance helper! I’m gonna have to check that out.
@AndrewM would this fix be something that would fix the error that I asked about it this thread? (I’ll have to try it the next time I see the duplicate code error)
I don’t think it will help with that issue. The ‘Selected Issue Helper’ basically gives you the same as what you see in the Customization Tool Dialog, script editor as well as the Custom Controls and Properties tabs from Custom XML Editor. The only reason I found I needed it was when it would fail to load the cusomization due to syntax errors.
Since the Read Only portion of the code it generated from the controls listed in the XML, I would open the XML editor, look through the ‘Custom Controls’ tab for the duplicates, make a note of the key, delete any properties related to the key then delete the control from the Custom Controls.
Bummer, thanks for responding.