I feel your pain Dustin! I've done that before.
Found it - My columndefs were under my listaction.
Yet another instance of a missing curley bracket.
Version 11, MVC
I cloned the getall method and the api works great.
I see my data coming back.
I created a table with one column, copied the datatables method from the page, removed all the columndefs except for one...
And no matter what I'm getting the infamous Requested unknown parameter '0' for row 0, column 0. For more information about this error, please see http://datatables.net/tn/4
My results look fine, I have an items array with a list of objects.
Does anyone have a suggestion on how to troubleshoot why this is not working?
My table:
<table id="MyRecordStateTable" class="table dataTable align-middle gs-0 gy-3">
<!--begin::Table head-->
<thead>
<tr>
<th class="p-0 w-50px"></th>
</tr>
</thead>
<!--end::Table head-->
<!--begin::Table body-->
<!--end::Table body-->
</table>
My datatables:
var dataTable = _$myRecordStateTable.DataTable({
paging: false,
serverSide: true,
processing: true,
listAction: {
ajaxFunction: abp.services.app.recordStates.getAllForUserId,
inputFilter: function () {
return {
userId: _userid
}
},
columnDefs: [
{ "defaultContent": "-", "targets": "_all" },
//{ targets: 0, data: 'fullName'},
]
}
});
What my items in the array of 'items' look like:
{
"recordState": {
"state": 2,
"notes": "",
"recordId": "08da5a0b-e079-4edb-8ebb-17fcb45292ae",
"recordCategoryId": "08da5a0b-deaf-4372-87a1-2320eb5fbc2f",
"userId": 10,
"recordStatusId": "08da5a0b-df28-4ff8-829c-185c1a27586f",
"id": "0c252a48-8208-a9cf-06dc-3a04c3460dcc"
},
"recordStatus": {
"statusName": "Accepted",
"htmlColor": "#67c777",
"csscLass": "",
"isDefault": false,
"tenantDepartmentId": null,
"id": "08da5a0b-df28-4ff8-829c-185c1a27586f"
},
"recordfilename": "auto insurance.pdf",
"recordCategoryName": "Auto Insurance",
"userName": "Marble 68",
"recordStatusStatusName": "Accepted",
"fullName": "Marble 68",
"userId": 10
}
I get multiple of these, and yet, no matter what, I'm getting that error.
I tried adding this, from the generated page:
_$myRecordStateTable
.on('xhr.dt', function (e, settings, json, xhr) {
console.log('data back');
//sortingUser = settings.rawServerResponse.sortingUser;
dataTable.rawData = settings.rawServerResponse;
//debugger;
});
Any advice of things I should check? I'm beating my head against the wall on this.
Thanks in advance for any advice!
Version 11.2.0 Core MVC
The user would add a widget that would display a table of data, and the table could be filtered by groups. The widget would show a table and the user could change a drop down at the top of the widget to choose which group is displayed. The filter would be specific to that instance of the widget.
The user could add multiple widgets, each with a different group as a filter.
Users can customize a widgets' settings on a per widget basis for views on their dashboard(s).
I thought about extending the widget object with a key value pair, so it'd store on in settings under Dashboard / Page / Widgets.
Is this the best way? Or should I create an entirely different entity that holds the serialized widget settings and use that?
Is there a 'best practice' for doing this?
Thanks for any advice, Chris
I don't know if it is any help, but the Dockerfile files are set to always copy in the downloaded solution, which means incremental builds are a bit pointless because the 'new' Dockerfile will trigger a rebuild of almost everything, every time.
Changing these to copy if newer while developing locally sped up my builds.
For what it's worth - we accomplished this by adding a project to the solution and referencing as necessary.
Depending on where / how you will want legacy data access, you can approach this by either adding references whereever you need this legacy data, or - create a service for it and reference it only there.
For example - You create a new project that connects to your legacy data. Then, you reference that in the .Core project. In the .Core project, you wrap the legacy data access with a service.
Your new legacy data service could then be exposed throughtout the architecture
Yes, this is the case.
One side effect of this the filter's always prepopulate with the date the page is rendered, excluding any results with a date time property from the results.
First view is always "today".
What needs to happen is they're only used as a filter if they're set.
This is a very bad user experience to have these set and used automatically.
Ah - I see - replaced with daterangepicker.
However, the templates in the rad tool apparently haven't been updated.
Is this correct?
In 11.0 - in bundles, there is:
"node_modules/bootstrap4-datetimepicker/build/js/bootstrap-datetimepicker.min.js",
"wwwroot/assets/bootstrap4-datetimepicker/defaults.js",
this is not in the 11.2 bundles.
MVC Core Jquery 11.2
Downloaded fresh project, did yarn / create bundles, used rad tool to create simple entity with a name and a datetime.
The resulting index.js throws a jquery error for .datetimepicker.
The datetimepicker library is not in the default bundles.
Should it be, or is a different library meant to be used?
If it should be, I'll can just add it - but before doing so I wanted to double check just in case.