What is QuickBooks Online

QuickBooks is an accounting software package developed and marketed by Intuit. QuickBooks products are geared mainly toward small and medium-sized businesses and offer on-premises accounting applications as well as cloud-based versions that accept business payments, manage and pay bills, and payroll functions.

Getting Started

In order to start, we will show several examples. ZappySys includes an ODBC JSON / REST API Driver that will help you to call QuickBooks Online API, read various data from QuickBooks Online with ODBC. To learn more about QuickBooks Online API check this help file. To access QuickBooks Online data using REST API call, you need to create an Intuit Developer Account and then create QuickBooks Online App.

Create an Intuit Developer Account

Follow the mentioned steps below to create an Intuit developer account:

1. you can visit this site developer.intuit.com, and click on Sign up from the menu bar.
2. A registration form will be opened in a Popup. you can fill up and then click on Create Account.
   

   Signup Form: Intuit Developer Account

3. Complete the validation check and click Continue.
4. On the confirmation dialog, provide a few details to fill out your profile and click All set.

Once you configured the data source in Gateway, we can now setup Linked Server in SQL Server to query API data.

1. Assuming you have installed SQL Server and SSMS. If not then get both for FREE from here: Get SQL Server Express and  Get SSMS
2. Open SSMS and connect to SQL Server.
3. Go to Root > Server Objects > Linked Servers node. Right click and click New Linked Server...
   

   Add Linked Server in SQL Server

4.  Now enter the linked server name, select Provider as SQL Native Client
5. Enter data source as GatewayServerName, PORT_NUMBER where server name is where ZappySys Gateway is running (Can be same as SQL Server machine or remote machine). Default PORT_NUMBER is 5000 but confirm on Data gateway > General tab in case its different.
6. Enter Catalog Name. This must match name from Data gateway Data sources grid > Name column
   

   Configure Linked Server Provider, Catalog, Server, Port for ZappySys Data Gateway Connection

   INFO:
   

   • For SQL Server 2012, 2014, 2016, 2017, and 2019, use the SQL Server Native Client 11.0 as the Provider.
   • For SQL Server 2022 or higher, use the Microsoft OLE DB Driver for SQL Server as the Provider.
7. Click on Security Tab and select last option "Be made using this security context". Enter your gateway user account here.

8. Optional: Under the Server Options Tab, Enable RPC and RPC Out and Disable Promotion of Distributed Transactions(MSDTC).

   

   RPC and MSDTC Settings

   ---

   You need to enable RPC Out if you plan to use EXEC(...) AT [MY_LINKED_SERVER_NAME] rather than OPENQUERY.
   If don't enabled it, you will encounter the 'Server "MY_LINKED_SERVER_NAME" is not configured for RPC' error.

   Query Example: EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]

   ---

   If you plan to use 'INSERT INTO...EXEC(....) AT [MY_LINKED_SERVER_NAME]' in that case you need to Disable Promotion of Distributed Transactions(MSDTC).
   If don't disabled it, you will encounter the 'The operation could not be performed because OLE DB provider "SQLNCLI11/MSOLEDBSQL" for linked server "MY_LINKED_SERVER_NAME" was unable to begin a distributed transaction.' error.

   Query Example:

   Insert Into dbo.Products 
   EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]

   ---

9. Click OK to save Linked Server
10. In SSMS execute below SQL query to test your connectivity.

    SELECT * FROM OPENQUERY( MY_LINKED_SERVER_NAME, 'SELECT * FROM $')

11. Here is the preview after you run some REST API query in SQL Server. Notice that you can override default configuration by supplying many parameters in WITH clause (second query example in the screenshot).
    

    SSMS Output - Query REST API via Linked Server OPENQUERY statement (Connect to ZappySys Data Gateway)

12. You can wrap your queries inside View or wrap inside Stored procedure to parameterize. Here is an example of creating the view which calls REST API queries.

    CREATE VIEW dbo.vw_MyAPICall_View 
    AS 
    /*Call REST API inside SQL Server View*/
    SELECT * FROM OPENQUERY( MY_LINKED_SERVER_NAME , 'SELECT * FROM $');
    
    GO
    

13. Notice in above approach if you parameterize Stored Procedure then check this article to understand Dynamic Metadata.
14. Now let's insert API data into the new data table "tblMyAPiData" in the SQL server database. For that, we need to execute below SQL query.

    Select * into tblMyAPiData FROM OPENQUERY( MY_LINKED_SERVER_NAME , 'SELECT * FROM $')

    

    Insert data into the new table

15. Let's insert and update records into the already created table "tblMyAPiData"
    • To do that first we need to insert the new API data into the "#temp_tblMyAPiData" temporary database table.
    • Now let's delete the old records from the database table which are updated.
    • At the last insert all new API data into the database table.
    • To do that, we need to query like below SQL queries.

    SELECT * into #temp_tblMyAPiData FROM OPENQUERY(MY_LINKED_SERVER_NAME, 'SELECT * FROM $')
    
    DELETE FROM [dbo].[tblMyAPiData] WHERE id in (SELECT id FROM #temp_tblMyAPiData)
    
    INSERT INTO tblMyAPiData
    SELECT * FROM #temp_tblMyAPiData

     
16. In the upper step, we see how to insert and update new records. Now if you want to update particular fields records only then you need to query like this.

    Update dbtbl_1
    set dbtbl_1.field1 = dbtbl_2.field1,
        dbtbl_1.field2 = dbtbl_2.field2
    FROM tblMyAPiData dbtbl_1
    JOIN (SELECT * FROM OPENQUERY(MY_LINKED_SERVER_NAME, 'SELECT * FROM $')) dbtbl_2 on dbtbl_1.id=dbtbl_2.id

    *NOTE: If you are getting error like : "Cannot resolve the collation conflict between “Latin1_General_CI_AI” and “SQL_Latin1_General_CP1_CI_AS” in the equal to operation" then you need to query like this :

    Update dbtbl_1
    set dbtbl_1.field1 = dbtbl_2.field1,
        dbtbl_1.field2 = dbtbl_2.field2
    FROM tblMyAPiData dbtbl_1
    JOIN (SELECT * FROM OPENQUERY(MY_LINKED_SERVER_NAME, 'SELECT * FROM $')) dbtbl_2 
    on dbtbl_1.id=dbtbl_2.id 
    COLLATE SQL_Latin1_General_CP1_CI_AS

     

Generate API Token

To access JIRA data using REST API call you need to generate an API Token in your Atlassian account. Follow the steps mentioned below to generate API Token:

1. you can directly login to the JIRA Atlassian Cloud site with your credentials, and redirect to the JIRA Atlassian Cloud Account's Profile Page for generating an API Token.
2. Click API tokens, then Create API token.
   

   Generate API Token - Step - 1

3. Create API Token - Give Label name to your API token which you are generating now
   

   Generate API Token - Step - 2

4. Use Copy to the clipboard, and paste the token into your or elsewhere:

   Note:  * For security reasons it isn't possible to view the token after closing the creation dialog; if necessary, create a new token. * You should store the token securely, just as for any password.

   

   Generate API Token - Step - 3

5. If you forgot API token, then you can Revoke your old API token and create new API token OR you can create multiple API tokens too.
   

   Generate API token - Step - 4

Now we have successfully generated an API token. Let´s start with an example. In this example, we will show how to read Tasks/Issues data from JIRA and store that data into a SQL table with SSIS.

About JIRA REST API

JIRA On-premises and Cloud Version both offers REST API. Here are some examples of JIRA REST API. For reading JIRA REST API data we will use JIRA REST API Search method which returns data in JSON format. Search API support use of JQL Syntax to filter issues. If you don't specify JQL parameters in /search endpoint then all issues will be returned. Check this link to learn how to build JQL for JIRA REST API Call. If you don't have JIRA hosted instance yet but still want to try REST API Examples on public JIRA Server then try below URL (Its official JIRA site which lists their own issues). For example, try to copy below URL in a browser and hit enter.

https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER

Step-by-Step: Import JIRA data using REST API 

Now once you have API token in the JIRA Atlassian Cloud website we can move to ODBC JSON Driver Configuration Part. For this example purpose you can use the following URL:

https://YOUR-DOMAIN.atlassian.net/rest/api/2/search?startAt=0&maxResults=100&jql=project=MYPROJECT

hence, your-domain is your Atlassian Cloud account’s domain name (we are using zappysys2.atlassian.net). Therefore startAt is the index of the first item returned in the page of results. And another maxResults is the maximum number of items that can be returned per page. Above all, each API endpoint may have a different limit for the number of items returned, and these limits may change without notice. (For more See this JIRA API Documentation for Pagination)

Configure Data Source in Gateway (ZappySys JSON / REST API Driver Example)

Now let's look at how to configure ZappySys Data Gateway. This feature acts as a bridge between Client App and ZappySys Drivers. Using data gateway you can use ZappySys Drivers inside applications / operating systems where ZappySys drivers may not be available directly for some reason (e.g. You don't have access to Server for Installation or System does not support ODBC drivers like JAVA programs). Click here to read more on various use cases of Data Gateway.

Configure Data Gateway User / Port

Now let's look at steps to configure Data Gateway after installation. We will also create a sample data source for ODATA API (i.e. JSON based REST API Service).

1. Assuming you have installed ZappySys ODBC PowerPack using default options (Which also enables Data Gateway Service)
2. Search "Gateway" in your start menu and click ZappySys Data Gateway
   

   Open ZappySys Data Gateway

3. First make sure Gateway Service is running (Verify Start icon is disabled)
4. Also verify Port on General Tab
   

   Port Number setting on ZappySys Data Gateway

5. Now go to Users tab. Click Add icon to add a new user. Check Is admin to give access to all data sources you add in future. If you don't check admin then you have to manually configure user permission for each data source.
   

   Add Data Gateway User

 

Configure Data Source

1. After user is added, go to Data Sources tab. Click Add icon to create new data source. Select appropriate driver based on your API / File format. You can choose Generic ODBC option to read data from ODBC DSN or use Native Driver option.

   NOTE: Whenever possible use native driver option for better performance / security and ease of use.

   

   Add Gateway Data Source (Native JSON Driver)

2. Now it's time to connect with JIRA. Let's use JSON Driver Data source with the following URL. Change domain with your own domain.

   https://{yourdomain}.atlassian.net/rest/api/2/search?startAt=0&maxResults=100
   

   ODBC JSON Driver: Enter Request URL
3. It is time to configure the Other Settings. Select HTTP Connection Type from the Connection Type drop-down and Click on Click to Configure Link to Configure the Connection Manager.
   [caption id="attachment_5596" align="alignnone" width="1245"] JIRA REST API Connection - Use ZappySys JSON Driver HTTP Connection[/caption] JIRA REST API Connection - Use ZappySys JSON Driver HTTP Connection
4. Now, we are going to set Pagination related configurations for JIRA Search request. Page number indicator must be startAt and maxResults value in URL must match with Increment By (i.e. 100)
   ODBC JSON Driver - JIRA request Pagination Configurations Settings
5. After adding pagination parameters let's add JQL= search parameter to get specific data. Here we are searching the data by Project name and status. You can find more information about JQL on this link: Search JIRA like a boss with JQL Here is example JQL search query for Public JIRA site. Replace jira.atlassian.com and project JRASERVER with your own values.

   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER
   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status=Open
   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status in (Open,Done)
   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status=Open order by lastViewed DESC

   Search using JQL parameter
6. Click on Select Filter to set the Filter.
   ODBC JSON Driver for JIRA API: Select Filter
7. You are done with the Configurations, Click on Test Connection to test the Connection.
   ODBC JSON Driver - Test Connection
8. After that select the table from where you want to get data.
   JSON Driver: Create Query of JSON data
9. Click on the Preview Data button to preview the data.
   Preview issues table data
10. And that’s it, Now we will move forward to the next Phase.

Build your Own JQL Search queries for JIRA Issue

In previous sections we saw some basic JQL queries to search JIRA Issues using API call. Now lets look at how to build such queries using online UI (Think like a query builder). from JIRA.

1. JIRA has its own public Issue repository which you can browse any time by going here https://jira.atlassian.com/issues/
2. Now try to change filter settings for search criteria (E.g. change Project, Status etc)
3. You will notice when you make change your URL keeps changing too. From that URL you can extract ?jql=xxxxxxx  part and use it as template for your own JIRA API search queries.

For more information check how to build JQL for JIRA REST API Call.

Generate API Token

To access JIRA data using REST API call you need to generate an API Token in your Atlassian account. Follow the steps mentioned below to generate API Token:

1. you can directly login to the JIRA Atlassian Cloud site with your credentials, and redirect to the JIRA Atlassian Cloud Account's Profile Page for generating an API Token.
2. Click API tokens, then Create API token.
   

   Generate API Token - Step - 1

3. Create API Token - Give Label name to your API token which you are generating now
   

   Generate API Token - Step - 2

4. Use Copy to the clipboard, and paste the token into your or elsewhere:

   Note:  * For security reasons it isn't possible to view the token after closing the creation dialog; if necessary, create a new token. * You should store the token securely, just as for any password.

   

   Generate API Token - Step - 3

5. If you forgot API token, then you can Revoke your old API token and create new API token OR you can create multiple API tokens too.
   

   Generate API token - Step - 4

Now we have successfully generated an API token. Let´s start with an example. In this example, we will show how to read Tasks/Issues data from JIRA and store that data into a SQL table with SSIS.

About JIRA REST API

JIRA On-premises and Cloud Version both offers REST API. Here are some examples of JIRA REST API. For reading JIRA REST API data we will use JIRA REST API Search method which returns data in JSON format. Search API support use of JQL Syntax to filter issues. If you don't specify JQL parameters in /search endpoint then all issues will be returned. Check this link to learn how to build JQL for JIRA REST API Call. If you don't have JIRA hosted instance yet but still want to try REST API Examples on public JIRA Server then try below URL (Its official JIRA site which lists their own issues). For example, try to copy below URL in a browser and hit enter.

https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER

Step-by-Step: Import JIRA data using REST API 

Now once you have API token in the JIRA Atlassian Cloud website we can move to ODBC JSON Driver Configuration Part. For this example purpose you can use the following URL:

https://YOUR-DOMAIN.atlassian.net/rest/api/2/search?startAt=0&maxResults=100&jql=project=MYPROJECT

hence, your-domain is your Atlassian Cloud account’s domain name (we are using zappysys2.atlassian.net). Therefore startAt is the index of the first item returned in the page of results. And another maxResults is the maximum number of items that can be returned per page. Above all, each API endpoint may have a different limit for the number of items returned, and these limits may change without notice. (For more See this JIRA API Documentation for Pagination)

Create ODBC – Zappysys JSON Driver Data Source

1. To do this, we will first open the ODBC Data Source : Select 64-Bit for 64bit apps and 32bit if your app / process doesnt support 64bit.
   Windows ODBC Data Sources
2. Click on Add button in User DSN Tab and then select JSON Driver from the driver list and click on Finish button to Create a new JSON Driver.
   ODBC User DSN Tab: Add new Driver Screen
3. Now it's time to connect with JIRA. Let's use JSON Driver Data source with the following URL. Change domain with your own domain.

   https://{yourdomain}.atlassian.net/rest/api/2/search?startAt=0&maxResults=100
   

   ODBC JSON Driver: Enter Request URL
4. It is time to configure the Other Settings. Select HTTP Connection Type from the Connection Type drop-down and Click on Click to Configure Link to Configure the Connection Manager.
   JIRA REST API Connection - Use ZappySys JSON Driver HTTP Connection
5. Now, we are going to set Pagination related configurations for JIRA Search request. Page number indicator must be startAt and maxResults value in URL must match with Increment By (i.e. 50)
   ODBC JSON Driver - JIRA request Pagination Configurations Settings
6. After adding pagination parameters let's add JQL= search parameter to get specific data. Here we are searching the data by Project name and status. You can find more information about JQL on this link: Search JIRA like a boss with JQL Here is example JQL search query for Public JIRA site. Replace jira.atlassian.com and project JRASERVER with your own values.

   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER
   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status=Open
   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status in (Open,Done)
   https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status=Open order by lastViewed DESC

   Search using JQL parameter
7. Click on Select Filter to set the Filter.
   ODBC JSON Driver for JIRA API: Select Filter
8. You are done with the Configurations, Click on Test Connection to test the Connection.
   ODBC JSON Driver - Test Connection
9. After that select the table from where you want to get data.
   JSON Driver: Create Query of JSON data
10. Click on the Preview Data button to preview the data.
    Preview issues table data
11. And that’s it, Now we will move forward to the next Phase.

Build your Own JQL Search queries for JIRA Issue

In previous sections we saw some basic JQL queries to search JIRA Issues using API call. Now lets look at how to build such queries using online UI (Think like a query builder). from JIRA.

1. JIRA has its own public Issue repository which you can browse any time by going here https://jira.atlassian.com/issues/
2. Now try to change filter settings for search criteria (E.g. change Project, Status etc)
3. You will notice when you make change your URL keeps changing too. From that URL you can extract ?jql=xxxxxxx  part and use it as template for your own JIRA API search queries.

For more information check how to build JQL for JIRA REST API Call.

In the previous section, we configured and added the ZappySys drivers in the ODBC Driver Administrator with information to connect to REST API. We queried the REST API data in JSON / XML format. Now let's look at how to import REST API data in Power BI using from ODBC connection.

1. Open Power BI Desktop and select the Get data option.
   

   Get data using Power BI

1. Once Get data is clicked, Go to Other and select ODBC.
   

   Import ODBC data source in Power BI

2. After that select ODBC DSN name from the DSN dropdown
3. Now it's time to import data. Basically, there are two modes to import data. Table Mode and Query Mode. Query mode is the most common but we will show you both ways.
4. Import using Power BI Query Mode:  Select your DSN and click Advanced Option to enter custom SQL Query to Import your REST API data. You can use ODBC DSN Data sources Preview tool to generate SQL Query. For example you can enter query like below. If you are not sure use Query builder (Found on Driver Preview Window)

   SELECT * FROM $
   WITH(SRC='https://my-api-url')

   

   Import JSON / REST API data in Power BI using SQL Query Mode

    
5. Import using Power BI Table Mode:  If you don't specify SQL query under advanced options then you may get a chance to select Table name to import and Credentials. If Power BI asks for credentials then select Windows and connect.
   

   Select credentials for ODBC Source

6. Once you enter select table, you can choose Select data to import and click OK (Below screeenshot is for the Table mode import when no SQL specified. You can pick desired table to import)
   

   Select Table to import in Power BI

7. You can also display data in map using Map visualization like below. Press the map and check Address this option will display the addresses in a map.
   

   See Address data in power bi map

   

   Map visualization in Power BI

8. Now, let's display data in Table Format. Select in values more columns and select the data grid to visualize the data.
   

   Select columns in Power BI

9. Once data is displayed, Right click on the data and select Show Data.
   

   Show data in Power BI

10. The data will be displayed
    

    read json information data

Generate API Token

To access JIRA data using REST API call you need to generate an API Token in your Atlassian account. Follow the steps mentioned below to generate API Token:

1. you can directly login to the JIRA Atlassian Cloud site with your credentials, and redirect to the JIRA Atlassian Cloud Account's Profile Page for generating an API Token.
2. Click API tokens, then Create API token.
   

   Generate API Token - Step - 1

3. Create API Token - Give Label name to your API token which you are generating now
   

   Generate API Token - Step - 2

4. Use Copy to the clipboard, and paste the token into your or elsewhere:

   Note:  * For security reasons it isn't possible to view the token after closing the creation dialog; if necessary, create a new token. * You should store the token securely, just as for any password.

   

   Generate API Token - Step - 3

5. If you forgot API token, then you can Revoke your old API token and create new API token OR you can create multiple API tokens too.
   

   Generate API token - Step - 4

Now we have successfully generated an API token. Let´s start with an example. In this example, we will show how to read Tasks/Issues data from JIRA and store that data into a SQL table with SSIS.

https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER

https://YOUR-DOMAIN.atlassian.net/rest/api/2/search?startAt=0&maxResults=100&jql=project=MYPROJECT

Once you configured the data source in Gateway, we can now setup Linked Server in SQL Server to query API data.

1. Assuming you have installed SQL Server and SSMS. If not then get both for FREE from here: Get SQL Server Express and  Get SSMS
2. Open SSMS and connect to SQL Server.
3. Go to Root > Server Objects > Linked Servers node. Right click and click New Linked Server...
   

   Add Linked Server in SQL Server

4.  Now enter the linked server name, select Provider as SQL Native Client
5. Enter data source as GatewayServerName,PORT_NUMBER where server name is where ZappySys Gateway is running (Can be same as SQL Server machine or remote machine). Default PORT_NUMBER is 5000 but confirm on Data gateway > General tab in case its different.
6. Enter Catalog Name. This must match name from Data gateway Data sources grid > Name column
   

   Configure Linked Server Provider, Catalog, Server, Port for ZappySys Data Gateway Connection

   INFO:
   

   • For SQL Server 2012, 2014, 2016, 2017, and 2019, use the SQL Server Native Client 11.0 as the Provider.
   • For SQL Server 2022 or higher, use the Microsoft OLE DB Driver for SQL Server as the Provider.
7. Click on Security Tab and select last option "Be made using this security context". Enter your gateway user account here.

8. Optional: Under the Server Options Tab, Enable RPC and RPC Out and Disable Promotion of Distributed Transactions(MSDTC).

   

   RPC and MSDTC Settings

   ---

   You need to enable RPC Out if you plan to use EXEC(...) AT [MY_LINKED_SERVER_NAME] rather than OPENQUERY.
   If don't enabled it, you will encounter the 'Server "MY_LINKED_SERVER_NAME" is not configured for RPC' error.

   Query Example: EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]

   ---

   If you plan to use 'INSERT INTO...EXEC(....) AT [MY_LINKED_SERVER_NAME]' in that case you need to Disable Promotion of Distributed Transactions(MSDTC).
   If don't disabled it, you will encounter the 'The operation could not be performed because OLE DB provider "SQLNCLI11/MSOLEDBSQL" for linked server "MY_LINKED_SERVER_NAME" was unable to begin a distributed transaction.' error.

   Query Example:

   Insert Into dbo.Products 
   EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]

   ---

9. Click OK to save Linked Server
10. In SSMS execute below SQL query to test your connectivity.

    SELECT * FROM OPENQUERY( MY_LINKED_SERVER_NAME, 'SELECT * FROM $')

11. Here is the preview after you run some REST API query in SQL Server. Notice that you can override default configuration by supplying many parameters in WITH clause (second query example in the screenshot).
    ODBC - Query API Data in SQL Server

    SSMS Output - Query REST API via Linked Server OPENQUERY statement (Connect to ZappySys Data Gateway)

12. You can wrap your queries inside View or wrap inside Stored procedure to parameterize. Here is an example of creating the view which calls REST API queries. Below View can be consumed like a normal table from any Tools or Programming Language which supports connectivity to SQL Server.

    CREATE VIEW dbo.vwApiInvoices 
    AS 
    /*Call REST API inside SQL Server View*/
    SELECT * FROM OPENQUERY( MY_LINKED_SERVER_NAME , 'SELECT * FROM $');
    
    GO
    

13. Notice in above approach if you parameterize Stored Procedure then check this article to understand Dynamic Metadata.
14. Now let's insert JIRA data into the new data table "tblissues"  in the SQL server database. For that, we need to execute below SQL query.

    SELECT * into tblissues FROM OPENQUERY( MY_LINKED_SERVER_NAME, 'SELECT * FROM $')

    Insert Data into the table
15. Let's insert and update records into the already created table "tblissues" .
    • To do that first we need to insert the new JIRA data into the "#temp_tblissues" temporary database table.
    • Now let's delete the old records from the database table which are updated.
    • At the last insert all new JIRA data into the database table.
    • To do that, we need to query like below SQL queries.

    SELECT * into #temp_tblissues FROM OPENQUERY(MY_LINKED_SERVER_NAME, 'SELECT * FROM $')
    
    DELETE FROM [dbo].[tblissues] WHERE id in (SELECT id FROM #temp_tblissues)
    
    INSERT INTO tblissues
    SELECT * FROM #temp_tblissues

     
16. In the upper step, we see how to insert and update new records. Now if you want to update particular fields records only then you need to query like this. In this query, We are updating "fields_duedate"  and "fields_issuetype_name"  fields only.

    Update dbti_1
    set dbti_1.fields_duedate = jira_2.fields_duedate,
    dbti_1.fields_issuetype_name = jira_2.fields_issuetype_name
    FROM tblissues dbti_1
    JOIN (SELECT * FROM OPENQUERY(MY_LINKED_SERVER_NAME, 'SELECT * FROM $')) jira_2 on dbti_1.id=jira_2.id

    * If you are getting error like : "Cannot resolve the collation conflict between “Latin1_General_CI_AI” and “SQL_Latin1_General_CP1_CI_AS” in the equal to operation" then you need to query like this :

    Update dbti_1
    set dbti_1.fields_duedate = jira_2.fields_duedate,
    dbti_1.fields_issuetype_name = jira_2.fields_issuetype_name
    FROM tblissues dbti_1
    JOIN (SELECT top 1 * FROM OPENQUERY(MY_LINKED_SERVER_NAME, 'SELECT * FROM $')) jira_2 
    on dbti_1.id=jira_2.id 
    COLLATE SQL_Latin1_General_CP1_CI_AS