You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The csproj provided in this repository does not matches the newer (M-Files External Object Type Data Source (beta) )
could you provide one sample which includes column mapping
The text was updated successfully, but these errors were encountered:
Koushiq
changed the title
Can you provide a sample for the latest M-Files External Object Type Data Source (beta) that includes column mapping!
Missing M-Files External Object Type Data Source (beta) Sample
Feb 20, 2023
I agree that having a branch showing this would be good (the older version could be kept as a separate branch). For now: you can find an example in the "Twelve Days of Code" solution (the "import gists" project): https://github.com/M-Files/TwelveDaysOfCode
I lied. This approach uses another approach. This sample is currently missing. I can add it to our backlog.
I'm not sure exactly what you're after, @Koushiq. You don't provide a column mapping in an external object type data source. Instead you expose the columns that the data source has, and the user then creates the column mapping when configuring the connection in their vault. This is because the configuration of each vault can differ drastically, so there's no way for your connector to know beforehand how it should be mapped.
To declare the available columns you should return them from DataSourceConnection.GetAvailableColumns, something like this:
The csproj provided in this repository does not matches the newer (M-Files External Object Type Data Source (beta) )
could you provide one sample which includes column mapping
The text was updated successfully, but these errors were encountered: