MxLoader

 View Only
  • 1.  Extraction timeout

    Posted 12-25-2021 09:20
    Hey guys, first off: Merry Christmas.

    Usually I extract data from Maximo using the web interface and exporting to CSV. Recently I found out MxLoader, and after figuring out how to set it up I'm able to access ASSET and Locations tables. The data loaded in Excel is correct.

    Although, when I try to access MXWO table after a while the program returns a timeout, but I can see all the fields I need, if I edit the Sheet.
    So, the data is there but somehow it isn't getting loaded in Excel. Max objects is set to 30 for testing purposes.

    Would I need to use SQL in D1 cell to limit the  WorkOrders displayed? If yes, how would the statement be like?

    Thank you

    ------------------------------
    Silva testes2
    testes
    ------------------------------


  • 2.  RE: Extraction timeout

    Posted 12-27-2021 09:24
    Hey Silva,

    Merry Christmas to you!

    Using a query is a good way to pare down data but if you're Maximum Objects is set to 30, this shouldn't be the issue. Are you querying the entire WO table (311 fields give or take)?
    A few things to try:
    1. Increasing the "Receive Timeout" field on your config sheet to 600.
    2. Use the REST service as opposed to OS
      1. A query using REST could be: worktype="PM"
      2. A query using OS could be: worktype='PM'
      3. Notice the difference in the single vs. double quotes for OS vs REST
    3. Reduce the number of fields you're querying

    Thanks,

    ------------------------------
    Matt McGuire
    Aquitas Solutions
    https://www.aquitas-solutions.com/
    ------------------------------



  • 3.  RE: Extraction timeout

    Posted 12-27-2021 09:51

    Merry Christmas!

    Go into workorderapplication in maximo, search the wo:s you want to export.

    Go to --> Advanced search - Where Clause

    Copy the clause and paste in MXLoader cell D1.



    ------------------------------
    Henrik Söder
    Nexer asset managemet
    ------------------------------



  • 4.  RE: Extraction timeout

    Posted 01-04-2022 05:04
    That solved the problem thanks :)
    But what if I need to extract certain WO? It throws an error:
    "Error on line 2: The content of elements must consist of well-formed character data or markup."

    Using this within the rest of the SQL syntax: and workorder.wonum >= 'XXXX-XX01' and workorder.wonum <= 'XXXX-X010'

    It should work because if I go to Advanced Search and insert that in the Where Clause, Maximo dashboard returns the correct elements.

    What am I doing wrong?

    ------------------------------
    Silva testes2
    testes
    ------------------------------



  • 5.  RE: Extraction timeout

    Posted 01-04-2022 07:50

    As Matt wrote:

    1. A query using REST could be: worktype="PM"

      So please try to use " instead of '
      And you also can delete tablename and just use columnname (WONUM instead of WORKORDER.WONUM) 


    ------------------------------
    Henrik Söder
    Nexer asset managemet
    ------------------------------



  • 6.  RE: Extraction timeout

    Posted 01-10-2022 19:23
    Edited by Silva testes2 01-11-2022 07:11
    I ended up solving that using the BETWEEN parameter.

    Although I'm getting another error while getting a specific range of WONUM:

    "Error 500: BMXAA4024E - The synonym value YEARS is not valid for the domain FREQUNIT, siteid=XXXXX, orgid=XXXXX. Specify a valid synonym value. You can find a list of valid values using the Domain application."

    EDIT: If I preview the data in Preview XML/JSON, it loads perfectly...

    EDIT2: Properly configured REST (at least it connects). But now, how can I transform this SQL query into OSLC (MXWO table)?
    ( istask = 0 and wonum between "XXXXXXX" and "XXXXXXX" )


    ------------------------------



  • 7.  RE: Extraction timeout

    Posted 01-11-2022 09:42
    Try using:

    istask=0 and wonum>"XXXXX" and wonum<"XXXXX"

    Page 17 of this file reviews querying ranges: Maximo REST API Guide

    Thanks,
    Matt

    ------------------------------
    Matt McGuire
    Aquitas Solutions
    https://www.aquitas-solutions.com/
    ------------------------------



  • 8.  RE: Extraction timeout

    Posted 01-11-2022 10:02
    Thanks for the quick reply.
    That did work. Thank you once again!!!

    ------------------------------
    Silva testes2
    testes
    ------------------------------



  • 9.  RE: Extraction timeout

    Posted 01-11-2022 10:08
    Excellent! Happy to help

    ------------------------------
    Matt McGuire
    Aquitas Solutions
    https://www.aquitas-solutions.com/
    ------------------------------