VEDA: Issues when synchronizing scenario file

[KristofferEML]

I am experiencing issues when synchronizing a scenario file related to the CmdF_bot attribute and using @CELL in Excel.

I have attached a generic scenario file which hopefully illustrates the problem. The point of the scenario file is to add a line of code to VTrun.cmd by using @CELL("filename";$A$1) in Excel to define the path that reflects the current user and model environment.

However, when synchronizing the scenario file in VEDA the path does not automatically update to reflect path of the current user environment. Instead, it appears that you have to make sure to manually open and save the Excel file locally before VEDA can update the path.  

I hope this makes sense. Is this a known issue, and is there a way to get around it?

Best,

Kristoffer

[AKanudia]

Aspose does not support the @CELL("filename";$A$1) function. In fact, I had trouble using this function even before we started using Aspose. I was trying to use parts of the sheetname to construct commodity names.

[Antti-L]

> Aspose does not support the @CELL("filename";$A$1) function.

I have been using CELL("filename") for many years in VEDA templates, and thus far I have not noticed any issue with it, unlike with the TOCOL function, which clearly was not recognized at all, and resulted in an error (see the recent thread by Till). My model data thus heavily depend on the values of CELL("filename").

@Amit: Do you mean that I do have a problem with using CELL("filename")? Or is it only arising if a recalc is in fact needed?

[kanbee]

Veda does not calculate formulas in files unless it really has to, which usually happens when Veda writes something back into the file (example: parametric and Fill-R), then it recalculates the whole file for the change to take effect. Other than that Veda only reads what has been last saved in the excel file by the user.

[KristofferEML]

Veda does not calculate formulas in files unless it really has to, which usually happens when Veda writes something back into the file (example: parametric and Fill-R), then it recalculates the whole file for the change to take effect. Other than that Veda only reads what has been last saved in the excel file by the user.

Thank you for the feedback. So I guess the solution is to add a dummy fill table in the the scenario file to ensure that VEDA updates and saves the path when synchronizing the scenario files. 

In my case, adding the following nonsensical fill table seems to do the trick terms of automatically updating the cell() function when synchronizing the model in VEDA. 


Best,

Kristoffer