# 6.2.2999 ## New Features ### Databinding a Repeater Controls inside of a Repeater can now be two-way data-bound to the properties of an object. That means if the user changes the value in the control, the value of the item in the dataset bound to the Repeater also changes accordingly. Read [Introduction to databinding](https://community.stadium.software/community/t/introduction-to-databinding-part-1/192) for more details on this. ### Web Service Body Type A type can now be assigned to the body of a web service operation thereby removing the onus on you to format the body as a specific JSON value. Should the value differ from the expected type, Stadium will automatically transform it into the expected type for that web service operation. Watch this space as further enhancements to the web service will be rolled out in the new year. ## Improvements * OAuth: Improved security around the handling of tokens * Allow setting a property on the ForEach.LoopValue * Change the Type Import dialog to contain a Name field and more descriptive text * Prevent periodically seeing an error page when refreshing Preview * When calling a connector, add the Object Editor to the parameter fields in the Property Grid * UX improvements to the Mapping Editor * ESC should close Code Editor and Expression Editor without saving ## Fixed Bugs * PreviewLogging prevented callbacks from running * The user profile icon was not visible when it overlaid a menu in deployed applications * Updating the server via the web frontend, frequently timed out. * WebDAV caused a 405 error when editing users & roles in deployed applications * ‘Expected a single value.’ validation was displayed when assigning an object or JSON string as value * Refreshing a selectable DataGrid in deployed applications caused an error: \[Type error: Cannot read properties of undefined (reading ‘selected’)] * Fixed an issue where the Object editor threw an exception ‘Value cannot be null. Parameter name: source’ --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.stadium.software/6/release-notes/6.2.2999.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.