Skip to main content

I have an MVIS dynamic array defined that has 24 items defined, whose locations are 1-24.

However, when MVIS send these to the subroutine, I am seeing 4 <blank> values coming in that I cannot account for:

Yes                    <--location 20
No                     <--location 21
F24                   <--location 22
<blank>
<blank>
<blank>
<blank>
220557            <--location 23
6.00                  <--location 24
I have tried deleting and re-adding the last 3, restarted the integration server & even changed the order of the fields but it continues to send the 4 blank values.
Any ideas of what might be causing this?  It has been fine up until this week when these last 3 fields were added.
Nelson


------------------------------
Nelson Schroth
president
C3CompleteShop LLC
Harrison OH US
------------------------------

I have an MVIS dynamic array defined that has 24 items defined, whose locations are 1-24.

However, when MVIS send these to the subroutine, I am seeing 4 <blank> values coming in that I cannot account for:

Yes                    <--location 20
No                     <--location 21
F24                   <--location 22
<blank>
<blank>
<blank>
<blank>
220557            <--location 23
6.00                  <--location 24
I have tried deleting and re-adding the last 3, restarted the integration server & even changed the order of the fields but it continues to send the 4 blank values.
Any ideas of what might be causing this?  It has been fine up until this week when these last 3 fields were added.
Nelson


------------------------------
Nelson Schroth
president
C3CompleteShop LLC
Harrison OH US
------------------------------

Well, I don't use MVIS so I'm talking from a position of ignorance here ... but I would start by checking your value "F24". Is the value strictly just "F24", or is it something like:

F24<vm><vm><vm><vm> or F24 <blank><blank><blank><blank>

where <vm> means Value Mark.

Cheers,

Brian



------------------------------
Brian Speirs
Senior Analyst - Information Systems
Rush Flat Ltd
Wellington NZ
------------------------------

Well, I don't use MVIS so I'm talking from a position of ignorance here ... but I would start by checking your value "F24". Is the value strictly just "F24", or is it something like:

F24<vm><vm><vm><vm> or F24 <blank><blank><blank><blank>

where <vm> means Value Mark.

Cheers,

Brian



------------------------------
Brian Speirs
Senior Analyst - Information Systems
Rush Flat Ltd
Wellington NZ
------------------------------

No, F24 is a SEASON/YR value (Fall 2024).

All we know is that the extra input array fields are NOT defined in MVIS but they are being sent by MVIS to the subrutine.  Must be MVIS "magic" of some kind.



------------------------------
Nelson Schroth
president
C3CompleteShop LLC
Harrison OH US
------------------------------

No, F24 is a SEASON/YR value (Fall 2024).

All we know is that the extra input array fields are NOT defined in MVIS but they are being sent by MVIS to the subrutine.  Must be MVIS "magic" of some kind.



------------------------------
Nelson Schroth
president
C3CompleteShop LLC
Harrison OH US
------------------------------

Nelson,

Does this also do the same thing when you try/test the service from MVIS ?

Can you share what the request looks like?  ( without exposing any sensitive information)

Either way, you may want to open a support ticket .



------------------------------
Mike Rajkowski
MultiValue Product Evangelist
Rocket Internal - All Brands
US
------------------------------

Nelson,

Does this also do the same thing when you try/test the service from MVIS ?

Can you share what the request looks like?  ( without exposing any sensitive information)

Either way, you may want to open a support ticket .



------------------------------
Mike Rajkowski
MultiValue Product Evangelist
Rocket Internal - All Brands
US
------------------------------

Hi Mike,

If I go to Swagger in MVIS for this subroutine, it acts normally using the generated JSON (all "string" values)...complains about token missing, etc.

As soon as I paste in the formatted JSON, and press "EXECUTE", NOTHING HAPPENS.  We tested the other MVIS subroutine and it is working as usual.

So, something about this subroutine/dynamic array is messed up under the hood.  I will create a case as you suggested.

Below is my MVIS Swagger JSON payload:

{
  "D365_WOJOURNAL_INFO_IN": {
    "D365ENDJOB": "",
    "D365ENTITY": "0100",
    "D365FGITEMID": "01224",
    "D365FGITEMQTY": "100",
    "D365RAFITEMQTY": "10",
    "D365SEASONYEAR": "F24",
    "D365SEEDMIX": "No",
    "D365SENDSEED": "Yes",
    "D365SITE": "GA",
    "D365STARTDATE": "05/28/24",
    "D365TRXDATE": "05/28/24 12:22:38",
    "D365TRXTYPE": "RAF",
    "D365WHSE": "T",
    "D365WOJOURNALID": "PRDJ000451",
    "D365WONUM": "WO-000968",
    "LINEDETAILS": [
      {
        "D365BOMITEMID": "14024BS",
        "D365BOMITEMQTY": "0.05",
        "D365BOMITEMUOM": "EA",
        "D365BOMITEMDESC": "CALADIUM CANDIDUMýNET TUBING 12in X 2000' RED",
        "D365BOMITEMLOTID": "220557",
        "D365BOMITEMQTYUSED": "6.00"
      },
      {
        "D365BOMITEMID": "NETPLYD",
        "D365BOMITEMQTY": "1",
        "D365BOMITEMUOM": "EA",
        "D365BOMITEMDESC": "CLIPPER STAPLES",
        "D365BOMITEMLOTID": "",
        "D365BOMITEMQTYUSED": ""
      }'
      {
        "D365BOMITEMID": "99991D",
        "D365BOMITEMQTY": "1.0",
        "D365BOMITEMUOM": "EA",
        "D365BOMITEMDESC": "UNKNOWN",
        "D365BOMITEMLOTID": "",
        "D365BOMITEMQTYUSED": ""
      }
    ],
    "SLICEEXPDATE": "05/29/24",
    "SLICEPICKAREA": "70",
    "SLICEWONUM": "1333139"
  }
}



------------------------------
Nelson Schroth
president
C3CompleteShop LLC
Harrison OH US
------------------------------