Daniel Bertocci

Sure: `FROST-Server.Core Version: v2.2.0-2-g485287a` This is the full log: [log.txt](https://github.com/FraunhoferIOSB/FROST-Server/files/12873286/log.txt)

I found out the issue and it is caused by a small inconsistency: _persistence_idGenerationMode_thing=ServerGeneratedOnly_ is case sensitive and to make it work has to be _persistence_idGenerationMode\_**T**hing=ServerGeneratedOnly_ with Thing in capital...

Temporary workaround until it is fixed: - Install the package - Go to \node_modules\@azure\ng-deploy\out\ng-add\schema.json - Change **id** into **$id**

I see that there are updates about this topic: [Announcing Native Azure Functions Support in Azure Container Apps](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-native-azure-functions-support-in-azure-container-apps/4414039?utm_source=chatgpt.com) > A new hosting method for running Azure Functions directly in Azure...

@borg1310 one option you may use is [EntityLinking](https://fraunhoferiosb.github.io/FROST-Server/extensions/EntityLinking.html) but it is not available yet for one-to-many relationship. If _sourceRelatedDatastreams_ has always a fixed amount of elements (e.g. always 3 datastreams),...

First of all, thank you because you gave me an immediate way to solve the issue we had. This issue was really hard to find out, it needed some steps...

@mamadshni @Ic3b3rg have updated storybook to the latest stable version? The reason why this issue was closed is because it was solved with this PR: #31772. After that, I've updated...

In front of FROST you can have an authorization layer that defines constraints for users using directly the same filter used in frost. I am going to provide a **very...

Thank you for pointing out that page, it is indeed useful for the example I pointed out. It is something that actually I have explored but I had good reasons...

@microsoft-github-policy-service agree