Skip to main content
N
Nou
July 25, 2022

Default load Method not sticking to replace - all time

  • July 25, 2022
  • 4 replies
  • 0 views

Hi all

We have come across an issue where the default load Method for workflow does not change from "replace" to "replace  all time". 

Anyone has experienced the same issue?

Thank you for your feedback

Nouria

4 replies

M
Marcello
July 25, 2022

Hi Nouria,

I was going to post a similar request because the system seems to load always in replace even if we select "Append".

I believe there is an additional setting to drive the load method.

Thanks in advance for the help.

 

Marcello

 

 

 

P
PahulSharma
July 26, 2022

Hello Nouria and Marcello,

Please check sourceID which plays an important role if you are loading data. If you are using same SourceID in consecutive loads, data will always get replaced. To avoid the same, always try to use a unique SourceID. 

M
Marcello
July 26, 2022

Hi Pahul,

I tried to change the source ids but with no results.

1st load is statutory


Marcello_0-1658844373756.png

 

2nd load id bybu and "Append" method


Marcello_1-1658844439853.png

The result is that data is replaced.

 

Do you think this is a bug? I am working on 6.6.0.

 

Thanks for the help,

Marcello

 

 

P
PahulSharma
July 27, 2022

I don't think it's a bug. Can you check if you have the same data unit on which you are loading data? That can be another reason for data replacement. To mitigate this you need to create separate channels for each load. 

N
NouAuthor
July 26, 2022

Hi all

I found out that this is logged as an ER and it is being addressed by OS. I am not sure when, but this is how it works for the time being. Changing The Default setting does not work under current versions.

 

G
GParreiras
November 20, 2025

Hi,

I still see this issue on verion 8.4. Even with the workflow profile set as Replace All time the drop down on the import shows Replace.

A
acapone
November 8, 2023

Anyone know when this will be fixed? Are we able to track the open item anywhere?

Terms & ConditionsAccessibility statement