Recently I’ve encountered an issue with the Lobby Element Designer. I’m trying to create a new Barchart element but started receiving “Unable to save element” errors when trying to save the new element. I’ve previously created Barchart elements, so I’m confident I have everything configured correctly in the Data and Formatting sections, but this one puzzled me enough to try duplicating an existing Barchart element. When duplicating a working element, I’m still presented with the same error when saving. This issue does not occur when working with other element types.
Does anyone know if there is a cache or some configuration that needs to be reset so that I can move forward with the development?
Regards,
Randy
Page 1 / 1
Hello EsiRandyG, Can you please provide screenshot of the error and your data source query?
Hi Bhanu,
Below are the requested screen captures. The part that has me baffled is I’m unable to even save a duplication of a functioning Barchart element.
Functioning Element
Duplicate of Functioning Element
“Unable to save element” error message
Datasource Definition
Hi all,
The weekend restart of the system resolved the issue. Curious to see if IFS has this noted as a bug or whether this has been resolved in a UPD already.
Marking this one as closed.
Regards,
Randy
Hi @EsiRandyG
I hope this reply finds you well.
If you face issue during the duplicate element I will suggest you create new element designer and also data source. after that you try.
FYI, I’m currently experiencing the same error in a customer environment (23R2), and it’s also affecting creating a brand new and very simple element.
The response from the server indicates that the error comes from Composite_Page_Repository_API, probably the procedure Save_Element, which starts with taking the procedure input and converting to an XMLType. It kind of seems like the conversion from JSON request to XML isn’t happening properly in the middle tier. We’re trying to schedule an environment restart, but I would also like to know whether it’s possible to refresh some cache or something.
We are on 24R1 and I experienced the same issue.
Here is a workaround, find a similar element and export the xml. Then edit the xml manually (change the ID, naem etc.). After that you can import the element again into IFS and edit the rest there.
