Certain API usage throws exceptions

FESAPI
21

I looks like a bug. Either on your side or (more probably) on fesapi side .

It would be helpful if you can post a code which would reproduce this bug as an issue on github : https://github.com/F2I-Consulting/fesapi/issues

22

OK, I will do that. I got no errors and export went through OK. But could it be, that it is because I am creating it with empty string for GUID? My understanding is that if we give empty string in the create APIs, then Fesapi will create a randomly generated GUID? I did that for all the create<…> APIs, and indeed it appears to work OK for things like properties, grid connection set representation, etc, so it may not be due to that reason.

23

Good catch!!

I just checked and it probably comes from the empty string for UUID.

Commonly, your understanding is right : an empty UUID is generated as a random UUID by FESAPI.

However, that’s not the case for partial objects. Indeed, a partial grid is important to represent a grid which exists somewhere but which you don’t want export. Since the grid exists somewhere, Fesapi assumes you know its uuid.
Then Fesapi does not create any UUID for partial grids.

So just provide an UUID and it should be fine.

Longer term, I am wondering :

  • if Fesapi should raise an exception if you don’t provide an UUID
  • of if Fesapi should create a random UUID such as for other non partial cases.
24

Thanks, that’s good to know. Either of the options you outlined sounds good.