I'm sorry, but I don't know how to write it any more clearly. To summarise:

1. Create a variable
2. Set the variable to the new file name using an Expression task...

Don't you just love it when you get a "urgent" work request that needs to be done "NOW", because it's impacting staff productivity, so you get the work done...

Just to elaborate, if you set up the other packages to run within a master package, you can then pass the variables that way.  If you're using SQL Server...

What do you mean by 'copy'? Where to? Where from? Using what tool?

Seems like the spam is ramping up again.

Please reread my post. I said use an Expression task to set the value of a variable. Once set in this way, the value will remain static.

Sure. Create a string variable and use an Expression task to set its value (using the code you pasted).

The rename and move can then reference the variable.

No. Only parameters can be shared, and only within a project (not across a solution).

How are you deploying your packages to the server? Are you using the project deployment model? If not, I suggest that you consider upgrading to it.

Please read here for...

I was able to reproduce this error. Have you had success setting this property by Expression in the past? Perhaps this is a property which cannot be parameterised ...

I've just been through this pain too ... VS2017 and still no easy way to re-order columns in a destination file.

Creating a blank file in the required format (just headers)...

when i ran the package through sql agent job  it got failed but i did not find any information in job history

Executed as user: . Started: 11:59:55 AM Finished:...

If the logic...

When packages run, they cannot update themselves, so a wholly package-based solution is not the way ahead.

However, your package can read from and write to a metadata table inside a...

I just reread your original post a little more closely. Your duplicates are in the source, not in the target, is that correct?

If so, the best way of handling this...