@@shristibhadouria4147 I recorded this one a while ago and don't recall exactly what I was doing, but if the use case is that every month you'll add another flat file, you want to do this: monthlyRaw is a dataset you overwrite with new data. Then, monthlyReal is the months you've previously loaded. Edgemart both, append, and register over monthlyReal. You'll probably want to manually run the dataflow when you do the load. If you run it and there's no new data, it will add the most recent month again and you'll get dupes. If that happens, I have a video for using computeRelative to flag and purge duplicates.
Hi, I am struck at append transformation, where the dataflow is getting aborted at Append Transformation and does the both the datasets at the time of Append should have same fields in same order
madhav arepalli the column structure needs to be the same, though summer 18 will solve that. In the meantime, check out my video "Children on a common grain" for how to merge tables with different structures.
I am just wanting to make sure I got this right. Basically, all you did was remove then re-add the registry when the data for the first batch was updated. In doing so, this will update the dataset is that correct?
I'm not following you, what part of the video are you referencing? I made this one about 18 months ago and would need to watch it again to get the context back.
@@LetsPlaySalesforce He is asking -- if you wanted the data to keep stacking onto the dataset instead of generating a new dataset every time you run a dataflow, what special thing did you do, other than delete the original register and create a new one? -- and how is this possible to automate?
Good Videos Pete
Hi, The next months's dataset/csv file will be added after the Overwrite node only as edgemart node ? Will the data be appended ?
or should be just replace sample batch_2 with sample batch_3? and then run the dataflow ?
@@shristibhadouria4147 I recorded this one a while ago and don't recall exactly what I was doing, but if the use case is that every month you'll add another flat file, you want to do this: monthlyRaw is a dataset you overwrite with new data. Then, monthlyReal is the months you've previously loaded. Edgemart both, append, and register over monthlyReal. You'll probably want to manually run the dataflow when you do the load. If you run it and there's no new data, it will add the most recent month again and you'll get dupes. If that happens, I have a video for using computeRelative to flag and purge duplicates.
Hi,
I am struck at append transformation, where the dataflow is getting aborted at Append Transformation and does the both the datasets at the time of Append should have same fields in same order
madhav arepalli the column structure needs to be the same, though summer 18 will solve that. In the meantime, check out my video "Children on a common grain" for how to merge tables with different structures.
I am just wanting to make sure I got this right. Basically, all you did was remove then re-add the registry when the data for the first batch was updated. In doing so, this will update the dataset is that correct?
I'm not following you, what part of the video are you referencing? I made this one about 18 months ago and would need to watch it again to get the context back.
@@LetsPlaySalesforce He is asking -- if you wanted the data to keep stacking onto the dataset instead of generating a new dataset every time you run a dataflow, what special thing did you do, other than delete the original register and create a new one? -- and how is this possible to automate?
@@RedIria you can build snapshots by edgemarting, appending new data, then registering to the dataset you edgemarted.
@@LetsPlaySalesforce Thank you, I will try this, but is there a way to do this in a recipe also?
@@RedIria the same principles should apply
Can you please make a video on flattening share table to set security predicate.
Are these the droids you're looking for? ruclips.net/video/QL-JbqUqfNY/видео.html
@@LetsPlaySalesforce exactly thank you so much.