This project has moved and is read-only. For the latest updates, please go here.
3

Closed

Ignore Null Reponses, avoid crashing

description

WallyAnchor wrote:
Hi

Your suggested solution would be ideal in this case. I can understand why you might not want to make it the default behaviour, but in my case it would be perfect.

I downloaded the source and while changing the code to match that behaviour (especially after you pointed out exactly what I needed to do and where to do it) was not difficult, I have a whole pile of errors in the project. A lot refer to missing assembly references - some of which I can easily resolve - others I don't know what I'm doing...). The other two main problems I had were "The name 'ComponentMetaData' does not exist in the current context" (or other component), and "no such method to override" - which interestingly only happened with VS2015, and not in VS2013 - leading me to think maybe I'm just using the wrong Visual Studio version?

Anyway, this is obviously beyond my capabililties, and I'm not expecting a tutorial!! I can write a console app to do what I'm wanting to do and at this stage it's probably the best approach, but it'd sit better in SSIS. I'm relatively new to SSIS and to be honest, I'm surprised it doesn't support JSON out of the box. Oh well.

Thanks
Wally
Hi Wally,

I might be able to add a "checkbox" allowing to bypass errors, such as "Do not crash on errors", that would be unchecked by default. That shouldn't be too hard to implement, but would require couple of weeks (at the time I am really busy so I am only dedicating couple of hours per day to fix existing bugs).
If you do not have any urgent need, you can wait for that.

Cheers,
Alberto.
Closed Nov 7, 2016 at 12:52 AM by webking
Added in the latest release!

comments

WallyAnchor wrote May 18, 2016 at 10:44 AM

I have a 'less than ideal' workaround for the meantime (a workable workaround nonetheless), but this change would be very welcome. I thank you muchly.

michaelfeldman wrote Aug 31, 2016 at 9:36 PM

Wally what was your work around?
I too am running into "Status code received was ServiceUnavailable, i.e. Service Unavailable" and it would prevent me from using the solution that I built:(
I think if the Json was still populated but with a string "no data" and integers would have -999 code that would help solve that issue

WallyAnchor wrote Sep 1, 2016 at 8:47 AM

Hi

My 'workaround' involved creating an executable that I used to process that part of my project, outside of SSIS. Less than ideal, so I'd like to see the above implemented, but workable nontheless.

But it would seem you're facing an entirely different problem. "ServiceUnavailable" would indicate you're not getting to the correct endpoint, or the service itself is down, rather than there simply being no data to return as was my issue.

Cheers
Wally