1,730
After upgrading to 2013R2, we can no longer enter a - in the Asset ID field. We have over 10,000 assets already in GP with a - i.e. asset ID is 10-44333. Why did Microsoft remove the hyphen ability from that field? And how can we modify all our existing assets to use a different field, I think that we will use A period (.) instead, i.e. 10.44333
Thank you for your help in advance!
*This post is locked for comments
Would it be possible to provide some more detail regarding your use of a macro in PSTL? What steps did you take? How did you run a macro in PSTL? Can you show us your macro script?
Thanks,
Angelo
I have experienced the same issue on after upgraded to GP 2013 R2 and resolved with using PSTL asset modifier.
But, PSTL asset modifier allow to modify only single asset at a time. So, I created a macro with word mail merge for all asset id which are all having hyphen and modified successfully by running macro in PSTL asset modifier window.
Note: You can use PSTL Fixed Asset Modifier with macro mail merge instead of updating from backend.
Hope this helps!!
L Like the script post from Tom Marttinen. I updated the script to run against all assets. I was unsure on the last statement, so I commented it out in my script. Here is my script:
update FA00100 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA00700 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA00701 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA00800 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA00801 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA01002 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA01100 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA01300 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA10200 set ASSETID = REPLACE(ASSETID,'-','_') where ASSETID LIKE '%-%'
update FA00800 set FROMASSETID = REPLACE(ASSETID,'-','_') where FROMASSETID LIKE '%-%'
update FA00801 set FROMASSETID = REPLACE(ASSETID,'-','_') where FROMASSETID LIKE '%-%'
update FA00800 set TOASSETID = REPLACE(ASSETID,'-','_') where TOASSETID LIKE '%-%'
update FA00801 set TOASSETID = REPLACE(ASSETID,'-','_') where TOASSETID LIKE '%-%'
update FA00800 set From_Master_Asset_ID = REPLACE(ASSETID,'-','_') where From_Master_Asset_ID LIKE '%-%'
update FA00801 set From_Master_Asset_ID = REPLACE(ASSETID,'-','_') where From_Master_Asset_ID LIKE '%-%'
update FA00800 set To_Master_Asset_ID = REPLACE(ASSETID,'-','_') where To_Master_Asset_ID LIKE '%-%'
update FA00801 set To_Master_Asset_ID = REPLACE(ASSETID,'-','_') where To_Master_Asset_ID LIKE '%-%'
--- update FA41700 set EVENTDSC = replace(EVENTDSC, 'ID: FENCE.0001/', 'ID: FENCE-0001/')
Update to Frank's script: if I look at what PSTL fixed asset modifier does when changing an asset ID, there are a few more tables than what Frank had identified. the problem is that there are some tables where we must change data in columns NOT called ASSETID.
update FA00100 set ASSETID = 'FENCE-0001'where ASSETID = 'FENCE.0001'
update FA00700 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA00701 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA00800 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA00801 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA01002 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA01100 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA01300 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA10200 set ASSETID = 'FENCE-0001' where ASSETID = 'FENCE.0001'
update FA00800 set FROMASSETID = 'FENCE-0001' where FROMASSETID = 'FENCE.0001'
update FA00801 set FROMASSETID = 'FENCE-0001' where FROMASSETID = 'FENCE.0001'
update FA00800 set TOASSETID = 'FENCE-0001' where TOASSETID = 'FENCE.0001'
update FA00801 set TOASSETID = 'FENCE-0001' where TOASSETID = 'FENCE.0001'
update FA00800 set From-Master-Asset-ID = 'FENCE-0001' where From-Master-Asset-ID = 'FENCE.0001'
update FA00801 set From-Master-Asset-ID = 'FENCE-0001' where From-Master-Asset-ID = 'FENCE.0001'
update FA00800 set To-Master-Asset-ID = 'FENCE-0001' where To-Master-Asset-ID = 'FENCE.0001'
update FA00801 set To-Master-Asset-ID = 'FENCE-0001' where To-Master-Asset-ID = 'FENCE.0001'
update FA41700 set EVENTDSC = replace(EVENTDSC, 'ID: FENCE.0001/', 'ID: FENCE-0001/')
Mr. Tom
Thanks for the update
Just to add up; since I am still looking for proper justification for the Hyphen, I have tested several special characters in the asset ID with no error at all, which makes the case quite questionable, why specifically the "Hyphen"
Until further findings, I do believe Mr. Frank's input is essential. I have just completed the update of a sample group of assets with no associated errors at all.
Well, I have now upgraded to GP2013 and came accross this issue. We have 15000 assets all with hyphen in them. Now I cannot type in an asset ID onto any GP FA screen. Nor can we use macros to update info.
From my point of view, our FA module at this point is non-functionable.
I went through MS support and there answers were:
1. delete all assets and set them up again. sure....and lose all history
2. use PSTL tool to change asset ID's. One by one. not practical
3. Procure their consulting services to help us....
I figure that an MS upgrade made our FA module non-usable...without any warning ahead of time. Nice.
Anyways, I am sure we will be using the table update suggestion above.
Thanks for the post....just ranting.
Here is my theory. GP 2013 added the ability to auto number assets. R2 added the ability to auto number assets by class id. I suspect that using special characters might interfere with auto numbering so they've been blocked. Any existing assets wouldn't be affected by auto numbering so they could stay as is.
Mark
Thanks Mahmoud. I aspire to be like you :)
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (