albertogeniola / ssis-json-source-component Goto Github PK

getting below error when clicking test
"Sorry, this functionality is still under development!"

Hi Alberto,

Thanks for developing this component! I was looking exactly for this one, but sadly it did not work for me, at this point. My setup is SSDT 2017 and SQL Server 2016. I initially tried using setup.exe, but it did not work - SSDT did not show the component in the toolbox. I tried, then downloading and compiling solution, using 4.7.1 and 4.5 as targets. After some play with referencing the assemblies compilation worked out. However, when I re-registered the assemblies and tried to make the data flow component to appear in the toolbox, it still did not work. I did try manual addition (e.g. Choose Toolbox Items) in each case, and I did get the assemblies (110,120,130) listed in under .NET section - and they showed some ... Advanced View linked to them. However when chosen, the SSIS toolbox, still failed to display JSONSource. Any suggestions would be appreciated.

Regards,

Michael S

when a json path is missing from a response the source and filter components fail is it possible to modify this behavior so the component will ignore missing paths and keep running

Hi,

I have a REST API POST call which requires a JSON input, and I could not figure how to pass a json object using the addin. Is it possible or at the moment only http key / value pairs are supported?

I have installed this component and got this problem, i cant edit existing components created by others users, but I can create new component in others data flows.

Any idea?

The message box for http error code handling errors when not filled out, but always creates a new row even when filled out, thus triggering the error.
The only workaround for this is to chose immediately stop or move to next request instead of retry.

How we can authorize a service, there is no way to provide username and password authentication

in sample screen SourceAdvancedUI Mode there is Direct Input. but I download latest version ONLY URL Input: Custom Value and From Variable (active) and From Input lane (disactive).

where is "Direct Input" field? and how to use local file json as the source Json in new version of your SSIS component?

My package runs fine when running within Visual Studio, but once I deploy to SQL Server, and run from within the Integration Services Catalogs, the job fails:

Any advice greatly appreciated!

Hi Alberto,

How far away is the proxy support?

Microsoft require TLS 1.2 to connect to OData endpoints in cloud applications such as Dynamics 365 SAT and Production environments. SSIS-Json-Source_Component runs under .NET Framework 4.0 which supports only TLS 1.0 by default.

As a short-term fix, it is possible to force TLS 1.2 in .NET 4.0 in Utils.cs by adding the following code just before the SendAsync request:
System.Net.ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;
You do require .NET 4.5 to be installed alongside .NET 4.0 for this to work.

A better solution is to upgrade the projects to use .NET 4.5 or higher, which supports TLS 1.2 with an enumerated value:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
SSIS runtime on SQL Server 2016 and 2017 installs .NET 4.5 so this should work.

.NET 4.6 supports TLS 1.2 by default without any code changes, but .NET 4.6 libraries are not available to SSIS yet.

A good feature request would be for a configurable TLS version option in the GUI.

In case anyone is wondering - I was able to use the manual install method and the dll's for 2016 on a Sql Server 2017 instance. I have only done a basic test from JSON file, but the parsing worked fine.

Ciao Alberto!

First of all, great component! Very nice...

I'm able to successfully iterate over an array. It is possible to also retrieve a single value from the root of the object?

For example:

{
next_page_token: "CqQCHgEAAFvPhHOo33Gu9bYlyYRj4sb_2xD7T2FG4Y0",
results: [
{
name: "Donald"
},
{
name: "Hillary"
}
]
}

I'm trying to get both the "next_page_token" and each value of "name".

Grazie,

Mark

The data-flow from the JSON Source Component after being sent through a Sort transformation component will hang indefinitely when connected to a Merge Join transformation component. The Sort works fine until you attempt to connect it with a Merge Join. When attempting to Debug the process will load indefinitely at this stage and no data will move through the Sort and Merge Join. When attempting to move the data directly into a table "Not using a Merge Join" the process works fine.

Thank you

Hi Alberto
I am using your SSIS-Json-Source-Component
And I came across a problem with a Json field inside the Json File
My problem is that I have Hebrew text in the value (in the inner Json field)
And when I try to import the field to my DB (Oracle) I am getting questions marks instead

If there are Hebrew letters in other fields (on the root of the Json), it's ok, and I can see the Hebrew letters fine.

For example –
{
"ID_TALMID": 1,
"NAME": "ליאור",
"ADDRESS_LIST": [
{
"CITY_CODE": 950,
"STREET_NAME": "אולפן"
}
]
}

The NAME field under the root displayed ok
The STREET_NAME which is inside a Json field under the root, displayed with "?????"

Thanks for your help.