''show Hierarchy Page'' Button gives error - dynamics-crm

I am administrator of a dynamics crm (on-premises) version 8.2.
A hierarchy rule was defined for "employee" entity.
The context seems to be set correctly, but clicking the "show Hierarchy Page" button leads to an error (attached screenshot).
"show Hierarchy Page" button
error page
In the development environment the button works properly, the error only appears in the production environment.
For other entities defined with hierarchical rules - the button works properly.
the error occurs from anywhere you can access the hierarchy page (from the views and the form), and for each employee type record. the error occurs in all browsers
I checked the definition of the hierarchy, and I transferred a solution to the production environment, which includes the relevant fields, relationships and hierarchy rules.
So far nothing has helped.
What else can lead to such an error?

Related

CRM 2013 Onprem: logged in users accessed area in CRM

We want to check what areas are used by user when they login to CRM. I have tried the recentlyvieweditems.
Is there any other way we can achieve this.
I do not think there is any solution or way to find out what area are clicked unless you login as that user and check what that user clicked.
The closest you can reach to get some insight for users and which entites they are accessing.
Organization insight solution
You have to capture those user telemetry data like - pages navigated, opened entity records, clicked ribbon buttons, etc using Application Insights or your own Database through your own API for all the breadcrumbs.
There is no other native solution other than Org Insights, that too available from 2016 onwards IIRC. Later they took different diversions during CRM online version upgrades.
You may try the EnableRule of application level command bar button to run your custom JS code to log user navigation. I haven't used it ever, but this is what I would try in your given scenario and I don't see any reason if it wouldn't work.
Create new custom entity/table with User ID/Name and URL attributes/columns
Create a application level command bar button
How do I add a global button (for all entities) on the CRM 2013 Command Bar
In button's enable rule, Add user id/name and document.location.href values as a new record to the custom table.
Create entity record through Javascript , CRM 2013 , SDK.Rest.CreateRecord
Don't forget to return false from the code in 'enable rule' so that the button should not actually be shown anywhere in the application.

apex application page not found

I created an empty application with project sample database in apex with administration and access control features.
Every time I create a new page for a table and want to run it, the page does not appear in navigation menu and when I run it from page editor an error occurs. (Report, master Report and etc.)
This problem does not happen in another applications I have.
Does anyone know why?
Something went wrong with the application creation process (perhaps an error occurred) or afterward to the application metadata (corrupted somehow).
When I created another new application, it worked fine.

Microsoft USD - Open different entities in a different tab

I have a Phonecall hosted control opened inside unified service desk as one of the tab and i have a few grids on that page.
On click of any grid inside my phone call page the respective entity is displayed on the same page.
Like for example if I click on customer product grid entity then that grid is opened similarly, there are other grids on which the user can click and it will load that entity on the same tab.
Now, the issue is as i said earlier that my new entity is being loaded on the same hosted control that is my phone call page. I want to prevent this from happening.
I want to display a different tab for whatever record is clicked within my PhoneCall Hosted control so this way my Phone Call Page is still there.
I know i can do this using Windows Navigation Rule but I will have to create different navigation rules for my different entities and then in future if any other grid is added in my phone call page then i will need to add another navigation rule to cater it. This is not the best approach, I want it to be dynamic. Is there any other way where I can open a different tab if a record is clicked from my phonecall page?
Create a new windows navigation rule. The "From" field should be your Phone Call Page. Leave the Entity, From search, and URL fields in the "Route Logic" section blank. Windows Nav Rules get executed in order, and once they find a match it stops executing. So make the order low enough so that it gets executed where you want it to.
The "Target Tab" and "Show Tab" fields should be a new hosted control that you want the popup to open in. The action is "Route Window".
As far as route type, you are going to have to play with this a bit. I think opening stuff from a subgrid is Route Type "Popup", but you might need to create 2 very similar rules (one with route type "popup" and the other with route type "in place") to account for all scenarios.
See the example screenshot below:

Dynamics CRM 365 seems to ignore default values for entity fields in quick create forms

For the contact entity I have set the default values for some build in fields to specific values. For example I set the default value for the field "Contact -> donotemail" to the value "Do not Allow".
In the "normal" web browser forms it seems to be working as expected.
But if I create a new contact using a quick create form and select the save and then "view created record" button the view switches to the new created contact.
If I then scroll down to the "donotemail" - field the field does not have the default value I selected in the field settings.
I googled the problem, the nearest community post I could find is
https://community.dynamics.com/crm/b/mohamedmostafacrmblog/archive/2016/06/02/set-field-default-value-in-microsoft-dynamics-crm-online-and-on-premise-using-business-rules-without-javascript-or-custom-components-plugins-or-workflows
Unfortunately the post is from 2016 and it describes how to workaround the problem using custom business rules. But due to this is build in funtionality there is no business rule I could edit and creating some new to achive the goal of setting a default value seems odd.
Did someone encounter this problem too and could find a solution?
One possible reason I could think of: you might have not refreshed the main window after publish all, maybe cached QC form didn’t work as expected bcoz “customize the system” will open a separate popup to edit & publish all.
Still technically server side should not be cached with old customizations. But QC might have rendered from cached Metadata in browser.
But publish all should reflect immediately & no delays expected. Make sure to refresh the main window next time :)

Reporting Services: come back from the sub-report to parent report and have it auto-run

The environment is SQL Server Reporting Services 2012. I have two reporting services reports: parent report lists some records and those records are presented and hyperlinks. These hyperlinks can be clicked and this will take you to a child report (for the clicked record). I also pass some parameters as part of the call to the child report and everything works fine.
On the child report I have a text box, which is a link back to parent report. I configured "Action" property for this text box to pass some parameters back (from the child report to the parent report). The problem is that after clicking "Back to Parent" link, the parent report doesn't automatically render. I have to select my parameters manually and click "View report" button in order to make it run.
How can I make parent report auto-render when I navigate back to it from the child report?
Thank you, bitnine, for your input! I do have somewhat complicated parameters in my report, some of which are cascaded. I had to ensure that all of them either had defaults specified or had values provided by the "Action" mapping (as specified on the sub-report's "Back to Parent" link. After that, things started working as expected.

Resources