Maximo 7.6.1.1 and Spatial 7.6.0.5:
I can load assets from the List View into a work order:
Create (Spatial) --> Work Order with All Records
Related info here: Creating sets of work orders and service requests
Unfortunately, this action is limited to 200 records:
BMXAA2333E - Please narrow your results down to a maximum of 200 rows to perform this action.
Is there a way to load more than 200 assets at a time into a multi-asset WO?
1) Go To > System Configuration > Platform Configuration > System
Properties
2) In the System Properties app, filter for "maxselectrows"
3) Expand the "webclient.maxselectrows" property. Set the "Global
Value" to 3000 or whatever you prefer.
4) Hit Save.
Source: Scroll arrows won't go past 200 items
Alternatively, for the customization route, see:
maximouiweb.war.WEB-INF.classes.psdi.pluss.webclient.beans.plusspss.PlusSConfirmSelectionDialogBean
In addition I had to increase "mxe.db.sqlserverPrefetchRows" as well.
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
I have a new Windows Application that I am adding Application Insights to. Adding a new chart gives the ability to Group on specific custom properties using a drop down. This drop down has 65 properties that AI must have added at some point. There were not specifically added.
We have a main AppInsights that takes all events. We've also created a AppInsight for development. The list of custom properties in the drop down is different between these two, even though the source code is the same.
It makes me suspect that there is some process that creates the drop down contents based on the incoming data.
The problem here is that the code has changed, and some properties are no longer available. We want to eliminate these values from the drop down, and add the new ones.
I am perfectly happy just deleting the entire list. Is there a way to do this?
The items that are available in the group by are properties that have ever been received by the back end in data you've sent, and aren't editable.
for custom properties/metrics, there's a limit on how many properties the backend will allow before it stops collecting new named custom properties. Conceptually, think of it as the backend storing an array of 200 elements for each telemetry item you sent, and mapping each custom property name to an index, and that mapping lasts forever. (i believe at the current time that limit is 200 each, but we're working on expanding that)
so if developers did things in your dev portal, even sent one item with custom property "foo", then that property will be there forever, and takes up one of those 200 slots. They can't be deleted or cleared at the moment.
Also, the contents of the group by box is also limited to events that have sent less than some threshold of distinct values, too. (I'm not sure on that exact value, but i believe it < 100 distinct values.) So fields like Id fields, or guids, etc, will eventually stop showing up as group by options, because the group by would create N distinct buckets of 1 item.
It seems like this would be something already mentioned in the App Insights UserVoice site, or documented in the azure documentation for group by but i'm not seeing it.
The only real workaround at this time is to create a new application insights resource in azure, and start submitting data to that new resource instead of your old one. And then you have to be proactive about never submitting custom properties that you're never going to use, or mixing case, as "Property1" and "property1" will be distinct properties...
If this is a big issue for you, i'd suggest submitting it to microsoft connect as a bug, or entering a uservoice suggestion above. I'll pass this on as something that really needs to be documented in the group by thing in the azure docs, too.
I am using Kofax Capture scan 10.o
Requirement is to set the default value in Create batch window setting pages per batch to 20 instead of 0 everytime the user open this window.
Please let me know how this will be possible.
I am not aware of how to customize this window.
Thanks.
I don't believe it is possible to set this programmatically. However you could write a custom Scan panel that pops up a warning if a batch is trying to close without 20 pages. This would essentially do the same thing as the product functionality, but then the user doesn't have to enter the number each time.
To write a custom panel you would need to look into the Capture API documentation and the sample installed to CaptureSV\Source\Sample Projects\StdCust\OCXPanel.
Update:
Daniel is correct in saying that "Pages per batch" is not a batch field. It is a property of the batch that must be set on the Create Batch dialog. To my knowledge this cannot be set programmatically: I did not see a mention of it in the API guide.
Actual batch fields can have a default set as you can see in the Batch Class Properties dialog below. It can either be an explicit string or one of the curly brace auto replace values. And yes, you should be able to modify them programmatically from a workflow agent. Or if using KTM, enable foldering in the KTM project and then batch fields are mapped to the root folder and can be modified in KTM validation or from script in any KTM module.
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.
I have developed a Web Interface for a db. The db and Web Interface are for my own use in my hobby running on my private intranet. Currently the db has 1800+ records which is going to increase with usage. Ver 1 of the Web Interface listed all records (~2.5KB) on a single page requiring a ton of scrolling. Vers 2 of the Web interface introduced pagination where records are grouped into a non-fixed size of roughly 100 records. On page load all 1800+ records are still transferred to the client but only the first page is "visible", the other 17 are hidden. I use a series of "non-submit" buttons with JS on-click functionality to hid the current page and make the selected page visible. Better in that scrolling is limited to ~100 records. Vers 3 only transfers the first page and the paging buttons on page load. Now, the on-click function using fetch() API sends a GET Request with parameters to fetch the desired page then swaps it into the DOM. The parameters specify a starting and ending points for the page. These values come from the paging buttons supplied by the server on page load. Works well with significantly reduced data transfer size. In Vers 4 I am generalize the fetch() API GET Request parameters to send user specified parameters to allow the user to choose any page starting and ending point. (Note: The user can not specify a page size directly.) So if the user selects a start and end point that no records fall into my plan is to use HTTP Response Code 204 "No Content" to tell the JS code that there are no matching records and nothing to swap. Is this the appropriate Response Code? Should I be including any other Header information in the Response with the 204 code?
Take a look at what the RFC says about 204:
https://www.rfc-editor.org/rfc/rfc7231#section-6.3.5
It's really intended for PUT requests. I think for what you are doing, it's fine to return 200 and no body, with a Content-Length header of 0.