Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: Tim MeagherHi,
First: You should never mix server and client versions.
The Excel file node was updated in LAE 4.5.2.
The node has both server and client components.
Therefore, in order to run this successfully, you need to run this against an LAE 4.5.2 server.
Otherwise, the node parameters and some of the node code will be using the 4.5.2 version, while the server based code will be using the (completely different) 4.5.1 version.
To give an idea about how much the node changed between 4.5.1 and 4.5.2, the 4.5.1 version was implemented in python, whereas the 4.5.2 version has a Java implementation.
Backwards compatibility is provided within (but not between) minor releases (e.g. within the 4.5.x branch but not between 4.1.x and 4.5.x) such that a graph created in an earlier version of the LAE will load correctly into a newer version of BRE.
Then, this graph will run correctly against the same newer version of the LAE server.
Similarly, BRX's created using an older version of BRE will run successfully against a later version of the LAE server within the same minor release (e.g. the 4.5.x branch).
The one exception to this rule is experimental nodes.
Experimental nodes are not fully supported and may change between versions - even within a minor release.
The Excel File node prior to 4.5.2 was experimental, therefore, there no guarantee is provided that graphs using the Excel File node in 4.5.1 will work correctly in 4.5.2. However, the interface changes to the node were made to limit the number of graphs that will be impacted by an upgrade.
If you have a working graph containing Excel File nodes in LAE 4.5.1, and you are upgrading to LAE 4.5.2, you should open the graph in a 4.5.2 version of BRE and then run this against LAE 4.5.2 and verify that the node still works correctly.
Regards,
Tim.