Stock data types selectively fail on refresh but do not flag which ones were not updated.

%3CLINGO-SUB%20id%3D%22lingo-sub-2735241%22%20slang%3D%22en-US%22%3EStock%20data%20types%20selectively%20fail%20on%20refresh%20but%20do%20not%20flag%20which%20ones%20were%20not%20updated.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2735241%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20latest%20windows%2010%20on%20a%20fairly%20current%20laptop%20and%20office%20365%20on%20a%20university%20group%20license%26nbsp%3B%20I%20guess%20you%20might%20call%20it.%20The%20stock%20data%20item%20is%20awesome%20but%20the%20operation%20of%20the%20refresh%20on%20error%20is%20sub-optimal%20to%20say%20the%20least.%20Please%20see%20the%20message%20on%20the%20screenshot%20attached.%20It%20says%20some%20lookups%20failed%2C%20but%20when%20that%20is%20the%20case%20the%20old%20data%20is%20retained.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Well%2C%20for%20investment%20purposes%20that%20is%26nbsp%3B%20truly%20dire%20as%20there%20is%20no%20indication%20which%20data%20is%20no%20longer%20current.%26nbsp%3B%20Therefore%20none%20of%20the%20information%20can%20be%20relied%20on%20after%20the%20error%20occurs%20without%26nbsp%3B%20looking%20up%20each%20one%20manually%20on%20the%20exchange%20and%20verifying%20it%20which%20is%20obviously%20what%26nbsp%3B%20the%20data%20type%20is%20meant%20to%20avoid%20us%20having%20to%20do.%20The%20error%20message%20(see%20attached)%20says%20that%20the%20backend%20has%20failed%20because%20%22we%20have%20changed%20or%20removed%20it%20on%20our%20side%22%20which%20is%20nonsensical%20-%20it%20is%20looking%20up%20the%20exchange%20supposedly.%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BPlease%2C%20please%2C%20please%2C%20flag%20the%20stock%20data%20item%20when%20it%26nbsp%3B%20fails%20the%20lookup%26nbsp%3B%20so%20investors%26nbsp%3B%20and%20analysts%20can%20readily%20see%20which%20ones%20have%20current%20data.%26nbsp%3B%3C%2FP%3E%3CP%3E--%20and%20is%20there%20a%20workaround%20to%20do%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2735241%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBI%20%26amp%3B%20Data%20Analysis%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExcel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFormulas%20and%20Functions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

I have the latest windows 10 on a fairly current laptop and office 365 on a university group license  I guess you might call it. The stock data item is awesome but the operation of the refresh on error is sub-optimal to say the least. Please see the message on the screenshot attached. It says some lookups failed, but when that is the case the old data is retained. 

          Well, for investment purposes that is  truly dire as there is no indication which data is no longer current.  Therefore none of the information can be relied on after the error occurs without  looking up each one manually on the exchange and verifying it which is obviously what  the data type is meant to avoid us having to do. The error message (see attached) says that the backend has failed because "we have changed or removed it on our side" which is nonsensical - it is looking up the exchange supposedly.

         Please, please, please, flag the stock data item when it  fails the lookup  so investors  and analysts can readily see which ones have current data. 

-- and is there a workaround to do this?

 

 

0 Replies