Ok, let me take a closer look.
‘Yes’ you changed something?
Hi,
That is bizzare. You didn’t change anything about the projects?
Hi,
I need an update on this issue please
Hi,
Well, you could run it too and you'll see the error too as I've given you access to the github repo and detailed out the steps to reproduce but I'll do that for you so here is the error.
'Volo.Abp.Http.Client.AbpRemoteCallException: An error occurred during the ABP remote HTTP request. (The operation was canceled).
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
If you're creating a bug/problem report, please include followings:
Hi,
I've created another test project showing the issue I am not having with being able to save a entity to the database. See the below link for the git repo and the steps to reproduce. What does not make sense is that I can call my custom application services and subsequent associated repository methods when the logic is in a class inherited from AbpViewComponent (Which is in the web project too) but not from just a normal class (DashboardStorageExtension).
Run the migrations associated with the solution Login as host user/admin From the Setup Menu click 'Setup' From the resulting Dashboard list page choose the 'New Dashboard' button on the right. Click 'Create' in the middle of the screen Drag a dashboard control onto the main part of the designer From the hamburger menu in the upper left click the 'Save' option
The error occurs in the DashboardAppService class on the below highlighted line. For some reason it cannot insert a new record into the table. I was able to get past the previous issue of the service itself not being injected properly but now it seems like I cannot do anything database related from my injected service.
I've given access to https://github.com/maliming for the git repository that contains the example project showing the issue
Hi,
Any update on this?
If you're creating a bug/problem report, please include followings:
I have 3 menu items at the 2nd structural level of my left side nav menu. The structure is as follows. As shown in the screenshot when I click the Test Sub Menu the 3 menu items belonging to Test Sub Menu do not show. If you want to reproduce this issue just add the below code to your class that implements the IMenuContributor interface.
Test Menu 1 Test Sub Menu Test Menu Item 1 Test Menu Item 2 Test Menu Item 3
Code to reproduce
var miMenu1 = new ApplicationMenuItem(
name: "TestMenu1",
displayName: "Test Menu 1",
elementId: "TestMenu1",
order: 1
).RequireAuthenticated();
var miMenu1SubMenu1 = new ApplicationMenuItem(
name: "TestMenu1SubMenu1",
displayName: "Test Sub Menu",
elementId: "TestMenu1SubMenu1",
order: 1
).RequireAuthenticated();
miMenu1SubMenu1.Items.Add(
new ApplicationMenuItem (
"TestMenuItem1",
"Test Menu Item 1",
"TestMenuItem1",
order: 1
).RequireAuthenticated());
miMenu1SubMenu1.Items.Add(
new ApplicationMenuItem(
"TestMenuItem2",
"Test Menu Item 2",
"TestMenuItem2",
order: 2
).RequireAuthenticated());
miMenu1SubMenu1.Items.Add(
new ApplicationMenuItem(
"TestMenuItem3",
"Test Menu Item 3",
"TestMenuItem3",
order: 3
).RequireAuthenticated());
miMenu1.Items.Add(miMenu1SubMenu1);
//Add Application Security Group menu item
context.Menu.GetAdministration().AddItem(miMenu1);
Hi,
I'm still confused by your response. As you previously stated (before I provided a solution) tiered projects will not work in the manner that I was trying to use it in. Now your taking random statements from my code and adding comments that seem to be at the very least out of context.
Since I gave an example on how ABP users can get around the issue I was having, this ticket can be closed. Please don't deduct from my support question quota.
Hi,
I'm a little disappointed with your answer overall as you are suggesting that if you use an ABP tiered solution approach you cannot use the DevExpress UI. I'm pretty sure if that were the case it would affect the number of organizations that use ABP's framework to develop their enterprise solutions with as DevExpress is a popular web control provider.
That being said I feel what you should have probably explained or suggested is that if DevExpress had a way to call the tiered solution's API layer from the misc. control's functions via JavaScript then all ABP's inherent functionalities would work as advertised as the Application layer would function as expected.
Simple answers like 'because tiered project' and 'you can use DevExpress ui in a monolithic application' are not very helpful to ABP's user base as it does not offer any possibilities of how to get 3rd party controls to work with ABP.
Despite this, after doing some more research, the solution to utilizing the DevExpress Dashboard control, was to call my ABP tiered solution's Web API layer by using JavaScript to find the 'Save' menu item on the Dashboard and overriding the .Click event with an ajax call to the API's endpoint.
In this way DevExpress will recognize ABP's 'Application Service' so you can pass along any relevant data to your ABP service while giving you access to all of ABP's build in dependency injected services.
JavaScript needed
function onBeforeRender(sender) {
var dashboardControl = sender;
dashboardControl.registerExtension(new DevExpress.Dashboard.DashboardPanelExtension(dashboardControl));
var toolboxExtension = sender.findExtension("toolbox");
if(toolboxExtension) {
var saveMenuItem = toolboxExtension.menuItems().filter(function (menuItem) { return menuItem.id == 'save' })[0];
if(saveMenuItem) {
saveMenuItem.click = function(s, e) {
//Save the variable
var xml = dashboardControl.dashboard().getJSON();
var apiurl = abp.appPath + "api/DashboardSample/Test/save-function/" + "123";
console.log(apiurl);
$.ajax({
url: apiurl,
type: "POST",
dataType: "json",
data: { dashboardDef: JSON.stringify(xml) },
success: function (result) {
console.log("Success!");
},
error: function (xhr, textStatus, errorThrown) {
alert('Request Status: ' + xhr.status + '; Status Text: ' + textStatus + '; Error: ' + errorThrown);
}
});
};
}
}
}
