I'm running a drill though report on multiple pages. Page1 contains the source report. A target report is on Page2. I want the target report page to only render when a specific data item value is selected in the source report.
Normally a Boolean value like this "ParamDisplayValue('Service Task Description') is not null", would work fine but I want it to be more specific than "is not null" because I am going to add more target reports running from specific data items in the same source report column.
I tried a Boolean value, [Service Tasks].[Service Task Description] = 'General Service Item' but it gives me an error when I select 'General Service Item' in the source report.
I also tried a Boolean value "ParamDisplayValue('Service Task Description') = 'General Service Item'. This does not give me an error but it will say "No data to retrieve" because I am now passing the parameter value and not the data item value.
I wish I could have the option in the drill through definition to pass both parameter and data item value at the same time but I can only choose one or the other.
Related
I been dealing with a very unfriendly situation and cannot wrap my head around it. I applied same approach to another entity and it is working as expected but not sure why I cannot get it to work with this particular entity.
I am creating a report in SSRS and wanna make sure once an end user opens a record Pre-filtering applies to the opened record. (Record is Release of information (Roi for short))
in my SSRS I created added a SQL data source named "MSCRM_DataSource"
then I added my DataSet which is this:
-DataSets:
+Release_Of_Information
In my data set I have a simple code:
SELECT Column1, Column2, Column3
FROM FilteredReleaseOfInformation AS T1
WHERE ROIid = #SelectedForm
Then I added another DataSet and Named it as below:
+CRMAF_RoiID
above Data set has this code:
SELECT ROIid AS FormID
FROM FilteredReleaseOfInformation AS CRMAF_RoiID
Then I went for my parameters and first added one Parameter as follow.
General Tab:
Name: "CRMAF_RoiID"
Data Type: "Text"
Select Parameter Visibility: "internal"
Default Values tab:
Specify values:
<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
<entity name="ReleaseOfInformation">
<attribute name="RoiID" />
</entity>
</fetch>
Lastly I added SelectedForm parameter as follows:
General Tab
Name: SelectedForm
Data type: Text
Parameter visibility: Hidden
Available Values Tab
Get values from a query
Dataset: CRMAF_RoiID
Value Field: FormID
Label Field: FormID
Default Values Tab*
Get values from a query
DataSet: CRMAF_RoiID
Value field: FormID
When I go to my test environment, report runs, but picks the first GUID in the query and not the associated record that is opened therefore no matter what record is opened it shows the info of first person RoiID.
**PS: Report is in my solution
**PS: I checked and ROIid is searchable on the entity
Is there anything that comes to your mind that I am missing? I spent so long researching and yet couldn't get this form work.
I have another entity that is working fine I do not know why this one has issue.
On your Dynamic-CRM check something and make sure the report is running on Current Record
if it is set on run for all related records Simply delete the report in your solution and add it again (preferably with a new name just add an _V2 or _V3 at the end of the name and set it up again.) this should do the trick as it did for me. I believe there is a bug in Dynamic CRM.
I’m new to SharePoint and PowerApps, can you help me on this one on how to resolve this issue?
I have my SharePoint list customized through PowerApps.
These are the dropdown columns that were set to automatically change value based on selection of one another.
BOG Disposition
Encoder’s Disposition
The scenario are the following below.
If BOG Disposition is equal to “Return (For Checking)” then the value of Encoder’s Disposition will automatically change to “Awaiting User’s Response” - This scenario is okay and working fine both for SharePoint and PowerApps but the problem is the second scenario.
Once the value of Encoder’s Disposition was now changed into “User’s Responded”, BOG Disposition must be changed into “Pending”. However, there is an error on formula saying “This rule creates a circular reference between properties, which is not allowed. A property cannot reference itself or other properties affected by its value”
I tried resetting the value of BOG Disposition but still not working.
I am working on a small COVID screening app. I have 2 lists in a single Sharepoint site:
BasicInfo:
ID (autogenerated by Sharepoint)
Name
Company
PersonalInfo:
BasicInfoID (a Lookup field to BasicInfo.ID)
Personal Phone
Personal Address
Company Phone
Company Address
All fields in both lists are required.
Creating the Powerapp, the BasicInfo form works as expected - records are populated in the Sharepoint list, and I can access the ID generated with BasicInfo.LastSubmit.ID after submission.
On the second screen of the app, I am having a hard time getting the "BasicInfoID" field populated. I am expecting to be able to set the value of BasicInfoID on the 2nd screen, then hide it, so the end user doesn't need to see (or populate) the value.
I have tried:
Setting the default value to BasicInfo.LastSubmit.ID, but I get an error of "Expected Record Value. The property on this control expects Record values. The rule produces Number values which are incompatible."
If I set the default value to BasicInfo.LastSubmit (no .ID), the form oddly submit - but the resulting data in the Sharepoint list doesn't show any value in the "BasicInfoID" field - it lists it as Required Info.
If I remove the automatically generated BasicInfoID field, I obviously get an error of "BasicInfoID: Field "BasicInfoID" is required."
I have added a Text field, assigned the DataField value to "BasicInfoID", set the default value to BasicInfo.LastSubmit.ID, but the form fails with the same error (BasicInfoID: Field "BasicInfoID" is required).
Thanks in advance!
When you do a LookUp from one SPO list (1) to another (2), the schema of the field in the list 1 is the same as the one returned by the Choices function. So in your scenario you can use this expression:
BasicInfoID: LookUp(Choices(BasicInfo, Id = BasicInfo.LastSubmit.ID))
The post at https://powerapps.microsoft.com/en-us/blog/default-values-for-complex-sharepoint-types/ has some more detailed information about using complex columns in SharePoint (such as LookUp ones).
Hope this helps.
I have a list report, and it pulls from a query subject that contains the following products: a, b, c, d, e. However, the report query contains a filter that filters for a, b, c.
Once you execute the report in HTML it displays products a through c as expected.
The issue is that once you click on the product column, create filter, the filter shows values a through e instead of a through c. Do you know how to fix this, so that you can't filter on products that don't exist in the report?
When you create a parameterized filter on a Report Studio report but don't create an associated custom prompt, Cognos will generate a system prompt for you. It will choose what it thinks is the right prompt type based on the data type of the item and nature of the filter. In the case of a value prompt it will display all available values, even if some values are already filtered out in another filter.
The solution is to create a custom value prompt on a prompt page that points to a filtered query as its source.
The rough steps are:
Create a new query that includes the data item that you want to filter
Filter the new query to only the values you want displayed as choices in the prompt
Create a prompt page, if it doesn't already exist
Add a value prompt to the prompt page and specify the parameter as the one you have in your main query filter
Configure the new prompt's 'Query' property to point to the new query
Set the 'Use Value' and 'Display Value' to point to the data item in the query
Now when you run the report you'll get a prompt page with a value prompt displaying only the values you want.
Here's my workflow:
An item gets added in a Sharepoint List (Say x). At that moment, a workflow triggers and starts a data collection task. For this task there is an Infopath fom which needs to collect some data from the user
This form has some fields which are to be fetched from the corresponding Sharepoint list item in list X and displayed in the form
I am trying to setup a data connection with the list X and fetching the fields of my interest.
However, the option "Include data for active form only" while setting up the connection is grayed out.
I am not able to get the right results in the form from the data connection, the data is not being returned for the right SharepointList item. THe data being returned is for the first item in list X.
Thanks!
This is because you are not passing a filter into the data connection. You are querying the list without an ID and since you are not selecting a specific list item it is just returning data from the first list item every time.
You are going to need to select a unique identifier and filter your result by clicking the add filter button and setting the foreign key = to primary key in list x. A quick google search of add filter to data in info path should give you an idea of what I am describing.
You may need to add a column in your initial table that imports the key from list x as a foreign key in your initial list.