RoyB
New Contributor III
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: How to update a record Using SQL SERVER UPDATE without updating identity field
figured it out. the ID field needs to be assigned to $original.ID The "orginal", which is case sensitive, lifts it into a sub-document in the json which is then ignored by the SET, but you are still able to include it in the WHERE (I had tried this already, but had typed it as Original, which didn't work, but revisited it once I found sometihng in the help for the SQL SERVER UPDATE Snap4.4KViews0likes0CommentsRe: How to update a record Using SQL SERVER UPDATE without updating identity field
With some more investigation, I've found that the tables we have been updating up till now are not declared as IDENTITY in SQL, but rather the third party that created the system have them working functionally as IDENTITY fields, but rather than let SQL maintain this, they do it in the backend of there system The new system I am currently trying to integrate too uses IDENTITY declarations, which implies that the way we have been updating has been wrong Any assistance with what the correct way is, would be appreciated.4.4KViews0likes0CommentsHow to update a record Using SQL SERVER UPDATE without updating identity field
The process established by the company I work for is that we have the document coming into a MAPPER, that links the incoming fields to the SQL SERVER UPDATE Snap. This tells the UPDATE snap which fields should receive which values, but this includes the identity field. I cannot exclude the identity field, because then the update fails because it does not have a value to compare in the where clause To put this into a SQL context: What I want to do: UPDATE table SET FIELD = value WHERE ID = id What the Mapper + Update is doing: UPDATE table SET FIELD = value AND ID = id WHERE ID = id And if I remove the ID field from the Mapper, then the pipeline fails because the field doesn't exist, but esentially I am trying to tell SQL to: UPDATE table SET FIELD = value WHERE ID = null This has only occurred on 1 of our servers, which is how I've discovered that the ID field is being updated on the other servers. We had assumed that Snap knew not to update the ID field. I am investigating SQL to see how the other servers are able to allow this on IDENTITY fields But I am posting here, because I am concerned that we are going about doing the updates, incorrectly Thanks for any assistance anyone is able to provideSolved4.4KViews0likes2CommentsHow to access error view document
Normally with our pipelines, if there is an error, we feed the error view document into an email, or a Jira object We have had a third party create a pipeline recently, and they have not done this We have had an error over night, and this is telling me to open the error view document, and I found a post online that suggests you can do this from the pipeline, but doesn’t give any details, and I can’t find anything in Snap Logics help, or anything else online Is this possible? And how do I do it? ThanksData goes null when updating CRM
I’m having an issue with a pipeline, and I’m hoping someone can help me with a solution The pipeline takes data from 2 different databases, and joins them, looks up from a third system, creates a new field, and thenupdates a field in CRM with that newly created value. Source data is our CRM system, and another core system, and a history table we create weekly This results in 50k+ records that need to be updated in CRM The whole pipeline takes 6+ hours to run The issue is: We select from CRM, because this is the record we will be updating to at the end of the pipeline However the error that comes up when I try updating is that the GUID field is null, which isn’t possible It’s a field that cannot be null, and I have investigated the pipeline and confirmed there is nothing that could make it null my best guess, is that the data I selected from CRM is timeing out someone, and becoming all nulls, while I am in the process of updating I’ve confirmed that some records were updated, whenever this has happened The pipeline usually works, this issue only occurs sometimes, and usually when I run it the next day it works fine I’ve had the pipeline time out anywhere from 4 to 9 hours When it runs without an issue, it usually takes 5-6 hours Has anyone else experienced something like this? Any suggestions or ideas on what is happening or how to fix it Thanks1.6KViews0likes1CommentRe: Exporting text file with CSV formatting, but with different numbers of fields
Thanks for the try, but it didn’t work. I modified my pipeline to use your method, and it does the same thing. The incoming document has a format of: 6 columns 33 columns (multiple rows) 6 columns And then somewhere between the csv formatter and the File Write it turns into 6 columns 33 columns (multiple Rows) 33 columns4.4KViews0likes1CommentRe: Exporting text file with CSV formatting, but with different numbers of fields
I’ve tried changing the mapper to do this instead: to strip out the 2 fields, and it does do it, but in the resulting text file the header row has only the 6 records I want, but the footer row has 33, presumably taking the additional columns from the preceding data row4.4KViews0likes0Comments