Is it true that your newly-uploaded DataSource isn't necessarily available when the upload is complete?
I have an ASP.NET app that is successfully uploading user-defined points (just one test point, currently) to the MapPoint Web Service. I know that the attempts are successful because (1) I receive a JobState enumeration return value of CompletedSuccess, (2) I make my upload call "synchronously", meaning my function does not exit while I have a JobState == Pending or InProcess (which is why I do indeed get a Completed job code return value), and (3) I have a browser window pointed at the CSS site, and I can actually see my new DataSource appear in my list of Staging DataSources.
After I receive a successful JobState, I immediately try to make a call to a FindNearby(), using my newly-uploaded DataSource's DataSourceName and EntityTypeName.
This call *always* fails, with a SoapException whose message text reads like:
"Either the specified data source does not exist, or your subscription does not allow you access.
For information on upgrading your subscription, contact your MapPoint .NET representative."
Now, the MapPoint CSS site currently has a bulletin about outage and latency, but these bulletins specifically mention the Render service--I'm targeting the Find service.
What I'm trying to do is a failure if I cannot programmatically detect the "real" moment at which a user is able to execute a Find on the DataSource he just designed and uploaded.
I thought my answer was waiting until I had a successful JobState value, but apparently not.
Is there anything else I can do? Is there any way I can really upload points and have them immediately, reliably available?
Thanks very, very much for any help.