The problem I have with this solution is I use a GCV to contain the starting point to start incrementing from since we don't won't to reuse any accounts. Since it is a GCV, that means I have to manually update the value every so often and restart the driver so we don't end up reusing an account that was deleted. What I am wondering is if there is somewhere else I can store a counter that can be read/written to from policy that will not be lost on a driver restart. I see there is a DirXML-PersistentData attribute on the drivers that it appears the drivers read/write to so not sure if there is a way to read/write to that location in policy or if there is somewhere else better suited for this purpose. If there is somewhere that I could write to from policy then I could store the number in their so it will always have the last account number that was created and I wouldn't have to use the unique name token to loop through to find the next open number.
Thanks in advance.
<token-unique-name counter-digits="5" counter-pad="true" counter-pattern="first" counter-start="~XX-start-counter~" counter-use="always" name="uniqueID" on-unavailable="error" scope="subordinates">
<token-map dest="RDN" src="Account_Type" table="..\..\Mapping Tables\Account Types Table">