web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / [SSIS.Pipeline] Error:...
Microsoft Dynamics CRM (Archived)

[SSIS.Pipeline] Error: No object exists with the ID -1

(0) ShareShare
ReportReport
Posted on by binoyk 61

Hello,

I am trying to insert (upsert) data using KingswaySoft to CRM Dynamics 365 On-premise. 

During whole process all components are executed without issue and shows green upto end.

But when I stop my debugger it shows error as mentioned in subject line. For testing I am trying to insert five records but that fails.

I KingswaySoft component, I selected option to "Redirect row to error output" so that I can see what is causing the issue. But data row has no error description.SSIS-Pipeline-error.pngUpsert-in-CRM.png

*This post is locked for comments

I have the same question (0)
  • Bill Pfingsten Profile Picture
    Bill Pfingsten on at

    Hi binoyk.  Did you ever resolve this issue?  I am facing a similar issue with a KingswaySoft SSIS component.  Thanks!

  • binoyk Profile Picture
    binoyk 61 on at

    Hello,

    Between my OLEDB source and destination component which is kingswaysoft to insert the record, what I did was I mapped only columns which I was wanting to copy data from.

    I was getting that error because I was trying to map primary key column between source and destination entities. I removed that mapping and it was fine after that.

    And one more thing, select "Upsert" in Kingswaysoft connection editor. This would take care both insert or update operations and helps in avoiding duplicates as well.

  • Daniel Cai Profile Picture
    Daniel Cai 935 on at

    This is a Microsoft bug, which happens to design-time execution only (when it is executed from within Visual Studio), and it only happens to SSIS 2019 when a Data Viewer is enabled after the destination component (and it happens to out-of-box ADO.NET destination components as well). 

    We have reported the issue to Microsoft, hopefully a fix is coming soon. 

    Given the nature of the issue is specific to design-time execution only when Data Viewer is enabled, you can pretty much ignore the error. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans