@david.gaster Have you tried using ../../ProjectFolder/properties.expr?
Or you could move the file into shared folder.
No, my question isn’t about moving the file into the other project folder or referencing its path. Let me try to rephrase it.
Let’s say I have 50+ projects and I want to be able to dynamically read a properties file from one of those projects. Is there a way I can do that? I need to be able to actually access the functions from in those .expr files somehow.
It’s not feasible to move all 50+ files over as no one knows when they’d all be changing.
@david.gaster Got your requirement. Unfortunately you can’t pass library path from one pipeline to another but one work around I am thinking about is- in exp file path provide the full path of the expr file with Orgname, then it can be used. Provided you should have access on the project folder which contains the .exp . I have attached my pipeline, it might partially help you 🙂
my custom.exp file contains below expression.
{
removeAttributeFrmOject : (subObj,keyToRemove) => subObj.filter((value,key) => !key.contains(keyToRemove)),
}
readExpFromDiffFolder_2020_10_01.slp (4.9 KB) it might help you partially.
@Supratim Thanks for taking your time to try and help. 🙂 But unfortunately this isn’t the use case I’m trying to solve. It appears there may not be a solution to my use case
