Dataverse for Teams
3 TopicsIssue with Access & Dataverse Long Text Field in aggregate function
Hi all - I've manged to migrate my MS Access application to Dataverse for Teams. Some things required work arounds, and found solutions for almost all, bar this final one issue. I needed to add a new text field to Dataverse to store some text comments. In Dataverse I made this a multiple lines text column. MS Access recognised it is a "Long Text" column. The problem is, that I need those comments to appear alongside other columns through an exisiting Aggregate query. Rather than showing this new column content, I only see the GUID identifier, and issue which I'd never seen before. After some trial& error, the problem seems to stem from the new field being added to Group By in the SQL aggregate query. From what I gather after searching, MS Access cannot run a Group By on a Long Text field... (1) is that behaviour correct/expected? (2) I then tried as dataverse columns, "Text Area" and "Text (with 4,000 characters)" , each of which is recognised as Long Text in Access and therefore throws up the same issue. Assuming it is indeed the Long Text in a Group By query, any other workarounds that may help here? thanks!572Views0likes0CommentsMigration to Dataverse
Hi all, I was able to migrate the backend of our MS Access application from Sharepoint Lists to Dataverse for teams, using the new connector tool. After export, in MS Access the reading of the records & all read queries works fine, and I can edit records provided there is only 1 table underlying the form. However, as soon as I want to edit a recordset via a MS Access form where there is more than 1 linked table being edited, I get the error "this recordset is not updatable" (the data shows fine, it's just not editable). I suspect an error in the relationships after export. However, from what I can see all the relationships were copied as expected and exactly as they were before export (but it's not so easy as the primary keys are different for dataverse, and the relationship is "indeterminate"). In Dataverse, the relationships also appear. I have since tried an export to Dataverse (instead of dataverse for teams), same issue, and I've rebuild the database from a new file and then export that, with the same issue. In a new Access file, I've imported the dataverse tables, and it imports correctly all tables and all relationships correctly, but the issue persists. I've ran out of ideas what to do to solve this...Suspect it's a bug. Any further suggestions?Solved2.2KViews0likes4Comments