You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I am creating a resource with a single region which has one name and its root node has other “actionresourcepoint” as region name and “root” as node name.
I add a new region with .name=“root” and .RegioName=“ActionResourcePoint” then add it to the resource using .add method.
when I write the resource in .lsx everything is ok however if I write it in .lsf both the region name and the root node has “root” as a id (same resource saved two times in each format).
What I am doing wrong or is it a saving error?
I Iam using resourceutils.Save method for both
The text was updated successfully, but these errors were encountered:
Did the following test also to be sure I did not made a mistake.
Wrote the resource as lsx (everything ok, region id saved as actionrsourcepoint and root node id as root) using resourceutils.save
Read the lsx file into a new resource using resourceutils.load
Saved the resource loaded as lsf without changing anything using resourceutils.save
Load the lsf resource, the region id changed to root as well as the node remains as root.
other tests I did
I used the conveter after step 1) to convert the right lsx to lsf then used it again to convert back from lsf to lsx and again the region id changed to root
Hi. I am creating a resource with a single region which has one name and its root node has other “actionresourcepoint” as region name and “root” as node name.
I add a new region with .name=“root” and .RegioName=“ActionResourcePoint” then add it to the resource using .add method.
when I write the resource in .lsx everything is ok however if I write it in .lsf both the region name and the root node has “root” as a id (same resource saved two times in each format).
What I am doing wrong or is it a saving error?
I Iam using resourceutils.Save method for both
The text was updated successfully, but these errors were encountered: