We have about 200 parameter sets, if i add another parameter set the last parameter set will disapear from the "All parameter sets" list.
How can we increase the max parameter set limit in TFS 2018?
Im referring to the parameter sets you create in TFS under Test > Parameters.
//Kind regards NB
Related
I need to get all the items of a SharePoint list and send as JSON
But the default is 100
If I set a larger number like 10000 it gives this error on the flow:
The attempted operation is prohibited because it exceeds the list view threshold.
So I am trying to get it in batches of 350 items.
But how can I use the Filter Query to start at a position x and return y items?
I tried
$skip eq 350
But this error occurs:
Column 'skip' does not exist
I think your question has 2 layers to it.
To increase the number of items returned by the Get Items Actions from Sharepoint you need click on the three dots on the left side of the action, and then go to Settings and you will see the image below, then set the size to 5000, that means your Get Items action will now return a maximum of 5000 items.
$top and $skip - I am not too confident what you are trying to do with this but perhaps share a bit more context, it sounds like you want to build a dynamic pagination ? Please explain this part unless the first point already achieve what you were aiming for
We have been running a SSRS report subscription in share point integrated mode for last 6 months.It was fine. This report had cascaded parameters which is auto populated based on user's access.For data driven subscription the user name was passed and internally other 4 access level parameter which are each a multi select parameter get populated. From last few days subscription was not going out on schedule time and below error was displayed. Even if we pass only one user from the query who has all proper access we are still getting the same issue. Also the parameter name which is displayed having no default or user defined value get changed. we have checked most of the users and they have proper access i.e value derived for each of the cascaded parameters.
Error: This report requires a default or user-defined value for the report parameter 'XXX'. To run or subscribe to this report, you must provide a parameter value.
The cascading parameters are like below
AAA -> XXX->YYY->ZZZ
Earlier the error message said parameter 'YYY' was missing a value.
As users come and go and move positions you will inevitably run into issues with their access. What I would suggest is that for each cascading parameter, have a default value that gets selected when there are no actual values available. For example, the value could be "N/A". And the report should successfully run and return no rows. You could even add a No Rows Message to it.
I have a report that I developed that utilizes render variables as described here.
My prompt page has 3 check box groups filled with variables. My first box is set to required, as it contains key information that needs to be pulled. The 2nd and 3rd have optional values. When the report runs, it requires at least one of the options in box 2 and 3 to be selected.
Any idea?
If a parameter is referenced directly in a query data item, Cognos will force it's associated prompt to be required even if you set it to 'Optional'. If this is the issue, the solution is to use a prompt macro instead of the normal ?? syntax. You set a default value to pass if the prompt isn't satisfied. This allows the prompt to act like an optional prompt.
The minimum syntax is:
#prompt('prompt_name','string','')#
The third parameter is the default value. I have just used an empty string here but you could change this to whatever you want.
In my project, I use installshield to insert an environment variable during installation.
PEAK_LIMIT = 1000
However, if I change the value to say - 1500, then during re-installation with higher versions causes the value to be reset to 1000. Is there a way to preserve the current value 1500 instead of resetting?
Thanks
It sounds like you have a hard coded value in your Environment table. Substitute it out with a property that equals that value. Then use a custom action during the install to assign the current value to the property if it has a value. This way when MSI rewrites the environment variable it'll keep the value it read.
Another approach would be to create a second environment variable (PEAK_LIMIT_OVERRIDE) that has higher priority in your application. This way the installer can set the default value to what it thinks is correct and keep that apart from user controlled data.
I have a local option set (picklist) that is populated from a "Query CRM Data" query. The query returns all users. Currently, the number of users is greater than the records per page (set to 50), so only the first 50 users are displayed in the option set. I cannot change the default number of records per page as this would cause a big performance hit in the system.
Is there a way for me to be able to display all records in an option set (picklist) where the number of records is greater than the records per page setting? I need to be able to select multiple users at once, so I think that rules out the Lookup.
Any thoughts? Much appreciated. Thanks.
You mention "Query CRM Data" so I take it you're creating a Dialog. Unfortunately the answer is no, you can't exceed the 50 limit of option sets on a dialog. You can only go beyond this limit when you have control over the query execution (such as in javascript or C#).
So in short, you'll have to use lookups. And also, as MarioZG mentions, you can only select 1 option in a option set/picklist anyway, so a picklist doesn't solve your other problem.