Including some level of validation for web services, specifically APIs.
For example, the fact that a Bound/Unbound action of an API is set to return a complex type instead of a primitive, completely breaks the API.
This results in a 404 Not Found error for this API and there is no indication on why this happens, and someone has to check the code carefully and see if something is broken. Instead there could be a compiling error or at least a code cop warning.
Comments
Another example just found:Supose we have Subpage1, that is used as a part in 2 API pages, APIPage1 and APIPage2.Both APIs are part of the same group of API pages. Both have the same entityName and entitySetName for Subpage1, sharedSubPage.This results in a runtime error when trying to access either one of the APIs, stating "500 sharedSubPage cannot publish sharedSubPage because a different entity with the same name has already been added.".The error is not even raised when publishing the extension, only at runtime when trying to access the API.Also, if we try to change the entityName and entitySetName for Subpage1 so that it is not the same in both APIs, let's say sharedSubPage1 and sharedSubPage2, when trying to access both APIs now we don´t run into an error but we see that both supages in both APIs are called sharedSubPage2.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team