Jonas Cirotzki

@leventegal-she agreed :) showing an error and aborting the share operation is enough here I filed another issue w.r.t. better error messages happening on the remote instance: https://github.com/hzi-braunschweig/SORMAS-Project/issues/9956

@SahaLinaPrueger Can you try to get the Converter logs?

So I'm still waiting for the correct converter logs, once I have them, I'm going to close this and open one ticket in the converter repo @AndyBakcsy-she

``` 2022-07-29 10:26:07.333 ERROR 1 --- [nio-8080-exec-1] o.a.c.c.C.[.[.[.[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [/survnet] threw exception [Request processing failed; nested exception is de.symeda.sormas.exception.TransformationException: Ungültige GUID: External...

@SahaLinaPrueger When sharing a case from A -> B and then back from B -> A, do you still encounter an error in the SurvNet converter?

So went through the reproduction and it seems to work as intended:  So this is from A. I reported it, handed over ownership, changed the ID on the other...

Also I was not able to change the external ID to something not matching the regex at any point in time b/c it is always grayed out.

So I argue that everything works fine with deletion and sharing. The question is more how @SahaLinaPrueger was able to set the external ID to something invalid :smile:

Maybe we can solve this by introducing `sea-orm-cli entity init` analogous to `sea-orm-cli migrate init`? This would reduce the number of manual steps required of setting up a project, thus...

I just stumbled across this ticket and wanted to add my two cents: I couple of years ago, I wrote an audit/analysis tool (also in Rust) for SELinux policies as...