I am experiencing the same issue and I am quite urgently in need of a fix as the issues we are getting in the RC is too large to stay on and the versions in the last 6 months have been terribly bugged and overloaded with issues. Hoping that an update to 10.2.0 would resolve issues but now we are stuck with something that is even worse.... previous versions atleast gave us UI functionality and now we dont even have our custom functions available. Not all companies have the resources to resolve endless issues upon issues that gets shipped in what is supposed to be a stable version but is actually not ran through a basic level of QA.
Been a long time since there has been a stable release.
Deployed version:
Menu Options available
Even the authorizations are not available and only standard base applicaiton auths are loading:
Debug/Test version:
Menu options available
Auths available:
When is the official 9.3 release date planned for or will it move to version 10 directly?
Just want to know as alot of the 9.3 issues are not present in the 10.0 or 10.1 task list which according due dates will be the 11 Nov.
Hi @ismcagdas,
No errors at all.
Hi @ismcagdas,
How do we go about setting a refresh tim on the abp.event.on('app.dashboard.refresh', function()?
For instance having it trigger every 5min.
Thank you, Regards, AuroraBMS
Thank you, will give the above a try.
Apologies, I see the commit link now. Tested & Working
Just dropping the link here for the rest.
Thanks @ismcagdas
Hi @ismcagdas,
I see that the issue is fixed for milestone 9.3, is it at all possible for me to fix it on 9.2 with specific steps or will this only be resolveable on 9.3?
If yes, what steps can be followed to resolve this?
Regards, AuroraBMS
Thanks, will create it.
Hi @musa.demir,
That is great news.
Will it still be released this week or next week? Just want to start drafting a rough migration plan.
Also just a side question while entities linking are mentioned, why are the Primary Key values not able to be used for linking entities as a display value? This is something that forces extra linking columns to be added in scenarios like transacitonal documents with header and lines especially. DocEntry would be the Primary key of the header but now we specify an internal Id on the documenets which adds a bit of frustration at times. The same goes with string based primary key when adding master data. If we create an item code the unique value is specified twice, once for the item code field and once for the primary key field.
is it possible to make the primary key available for display purposes when linking entities?
Regards, AuroraBMS
The other thing that is not possible currently is Parent to Parent link.
Multi level "Recipes" is an example of this. Parent being part of another recipe. Master-Detail makes a great representation for data linking to each other in the same table.
The standard property navigation allows for linking the same table with a 1 to many concept. Parent | Child BOM 1 | BOM2 BOM 1 | BOM3 BOM 1 | BOM4 BOM 5 | BOM1 BOM 5 | BOM2 BOM 5 | BOM3 Not sure if this is something that should be possible currently but it throws a stack overflow.
