Activities of "exlnt"

When I goto my download page for my license I do not see .NET Core 2.0 as an option in the dropdown. Has the full ASPNETZERO upgrade to .NET Core 2.0 been released?

<cite>ismcagdas: </cite> Hi,

Can you lastly share your DTO which contains CountryId field ?

Thanks.

Your question just helped me find the root cause of the countryId error. This WAS in my DTO:

public int CountryId { get; set; }

I changed it to this NOW:

public int? CountryId { get; set; }

This resolved the error!

I have a couple of questions for support team on this issue.

1. Do I need to apply these type of IF conditions into every view I have where I have optional dropdowns?
2. If yes, this does not seem to be a sustainable solution. Is there not something that can be done within the underlying ABP validation module to account for such instances?
3. Is there anyway to debug the ABP validation/code that takes place, as that would be very helpful to find such issues as the one I reported on this thread?

I tried by applying the following code into my createModal.js file for Prospect.

if (prospect.AddressType === "null") {
                prospect.AddressType = null;
            }
            if (prospect.Salutation === "null") {
                prospect.Salutation = null;
            }
            if (prospect.Gender === "null") {
                prospect.Gender = null;
            }

I added one of these IF conditions for each of the dropdowns where I am getting the validation. It works for all but one of the one shown below?

if (prospect.CountryId === "null") {
                prospect.CountryId = null;
            }

App service POST values sent: [https://drive.google.com/file/d/0B5HAoiVVXzY7X2NvYWUzd3ZWcFE/view?usp=sharing])

Validation Error on country Id: [https://drive.google.com/file/d/0B5HAoiVVXzY7My1qN2dORUs4ems/view?usp=sharing])

It still keeps reporting the same error message on this one dropdown now. Even though a value of "null" is being set. This is completely baffling! :?

<cite>ervingayle: </cite> As a test have you tried to DisableValidation on the controller method? <a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Validating-Data-Transfer-Objects">https://aspnetboilerplate.com/Pages/Doc ... er-Objects</a>

Also on the views do you have an AntiForgeryToken? Something like: @Html.AntiForgeryToken()

I had similar issues with my jQuery forms but not specific to the 4.4 upgrade rather from aspnetboilerplate.

Thanks for your tips and suggestions. I tried the disable validation on the app service method that is getting called and it did not make a difference! As for the AntiForgeryToken I have never used that on any of my pages and as per what I read in the ABP docs, it is automatically included in all pages by the ABP framework. So not sure if that would make any difference. Thanks again!

<cite>ismcagdas: </cite> Hi @exlnt,

Can you appl changes in this file to your version (Areas/Mpa/Views/HostSettings/Index.js) <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/commit/1ffb32a129854c45ebed12958563f8ed3d528849#diff-0ee402dc6b494081c40364034de66cf7">https://github.com/aspnetzero/aspnet-ze ... 034de66cf7</a>

Thanks.

I can live with the issue on the maintenance page as I dont need to use it that often. I only showed that to you as example of the issue I am facing on my custom entity page. How does this fix apply to my custom entity form?

Well this issue is now solved! Not sure what happened, but I restarted Visual Studio 2017 and tried the same line of code and was able to compile without any errors! I deployed my updated app to the hosting site and was able to create the new tenanat without MSDTC error.

I just deployed my application to my hosting site and I was doing the setup for my domain from the "maintenance" page in the host application. Even on that page, I ran into the exact same error with a dropdown, see image below, on the edition dropdown. [https://drive.google.com/file/d/0B5HAoiVVXzY7S2VzMzMtVWZWdDg/view?usp=sharing]) If I choose an edition and then click SAVE, the error does not happen. So essentially you are forced to select something in the dropdown. This is an exact replication of the problem I am facing on my "prospect" entity form dropdowns.

<cite>ismcagdas: </cite> Hi @exlnt,

Sorry for the late response. Can you share input dto for UpdateCountry method ? We will check it.

Thanks.

@ismcagdas - Thanks very much for following up on this thread, I really do appreciate it! I was able to find errors in my log files that helped me find root cause of the validation errors. There was a conversion failure happening in JSON.Net.

I am trying to do the exact same thing, I need to put some seed data into my tenant DB tables. Is there any way to achieve this in the .NET Core solution?

I was referring to my last few posts on this thread. I was not getting any response to my issues. In general you do provide support.

I did not open new thread as issue was somewhat related.

I still don't have an answer on my validation issue I posted here. Let me know if you want me to post new thread for it?