Hi @joe.fme, that random number should be just the Feature Service ItemID. I wouldn't worry too much about it, you could just ignore it or even remove it manually, the Reader should work the same.
However it is weird what you're saying about the ItemID changing every day. Is somebody re-publishing the feature layer? I can't think of other reason why the ItemID could change. And that would explain why the job can't be run unattended and why that string is changing every time you add the Reader.
You can check the string through the ArcGIS REST Services:
Hi @joe.fme, that random number should be just the Feature Service ItemID. I wouldn't worry too much about it, you could just ignore it or even remove it manually, the Reader should work the same.
However it is weird what you're saying about the ItemID changing every day. Is somebody re-publishing the feature layer? I can't think of other reason why the ItemID could change. And that would explain why the job can't be run unattended and why that string is changing every time you add the Reader.
You can check the string through the ArcGIS REST Services:
Hi there,
As part of my wider GIS Team there shouldn't be any changes each day to the Feature Layer but that's handy to know where it comes from! Thanks for pointing that out. I tend to be more on the ETL side than the GIS side so more knowledge is handy.
It is odd, but until this morning I have not been able to run it scheduled - but I re-added the readers, removed the ItemID and it seems to be working. For now.
Appreciate the feedback!
@joe.fme The Feature Service ItemID is usually the most stable part of the Feature Service identifer. You should be able to read your feature service using only the ID.
