Content-Type: text/html; charset="us-ascii" Received: from BN0PR16MB4445.namprd16.prod.outlook.com (2603:10b6:408:154::9) by BL0PR16MB2612.namprd16.prod.outlook.com with HTTPS; Wed, 13 Oct 2021 17:24:57 +0000 Received: from BN0PR16MB4397.namprd16.prod.outlook.com (2603:10b6:408:150::18) by BN0PR16MB4445.namprd16.prod.outlook.com (2603:10b6:408:154::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4587.25; Wed, 13 Oct 2021 17:24:56 +0000 Received: from BN0PR16MB4397.namprd16.prod.outlook.com ([fe80::ad69:bf92:3a7a:d7b]) by BN0PR16MB4397.namprd16.prod.outlook.com ([fe80::ad69:bf92:3a7a:d7b%5]) with mapi id 15.20.4587.026; Wed, 13 Oct 2021 17:24:56 +0000 From: Rickie George To: Microix Support Subject: How to connect Microix to a new MIP database Thread-Topic: How to connect Microix to a new MIP database Thread-Index: AdfAVRjyC7xnQHb/TB6Gh5JH7o6Zlw== Date: Wed, 13 Oct 2021 13:24:55 -0400 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 04 X-MS-Exchange-Organization-AuthSource: BN0PR16MB4397.namprd16.prod.outlook.com X-MS-Has-Attach: yes X-MS-Exchange-Organization-Network-Message-Id: b79f32a0-650b-4194-f196-08d98e6e6023 X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 x-ms-publictraffictype: Email authentication-results: microix.net; dkim=none (message not signed) header.d=none;microix.net; dmarc=none action=none header.from=microix.net; x-ms-office365-filtering-correlation-id: b79f32a0-650b-4194-f196-08d98e6e6023 x-ms-traffictypediagnostic: BN0PR16MB4445: x-ms-oob-tlc-oobclassifiers: OLM:7219; x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:-1;SRV:;IPV:NLI;SFV:SKI;H:BN0PR16MB4397.namprd16.prod.outlook.com;PTR:;CAT:NONE;SFS:;DIR:INB; x-microsoft-antispam: BCL:0; x-ms-exchange-crosstenant-network-message-id: b79f32a0-650b-4194-f196-08d98e6e6023 x-ms-exchange-crosstenant-originalarrivaltime: 13 Oct 2021 17:24:55.8398 (UTC) x-ms-exchange-crosstenant-fromentityheader: Hosted x-ms-exchange-crosstenant-id: 047ca1d7-5314-4422-8db2-9017a42a0ba4 x-ms-exchange-crosstenant-mailboxtype: HOSTED x-ms-exchange-crosstenant-userprincipalname: ErLVT9+Yb5R+LY7TBk71T2LuDcKDk76HPSQNJ+hDKJDPxKzHkeCvSR/RPwSpN/pwd5Ogq2868pt8kiNnFO2rIg== x-ms-exchange-transport-crosstenantheadersstamped: BN0PR16MB4445 x-ms-exchange-crosstenant-authsource: BN0PR16MB4397.namprd16.prod.outlook.com x-ms-exchange-crosstenant-authas: Internal x-ms-exchange-transport-endtoendlatency: 00:00:01.6033714 x-ms-exchange-processed-by-bccfoldering: 15.20.4587.026 X-Microsoft-Antispam-Mailbox-Delivery: ucf:0;jmr:0;auth:0;dest:I;ENG:(910001)(944506458)(944626604)(750132)(520011016)(706158); X-Microsoft-Antispam-Message-Info: yKwR5fDCPTtpbzSLwjdY+FIkb9/eos+Zoo2IG91K5vQTJkm1PECLFgbMni1MbxPRSDRWeYF88PfjpWku7/cwuVToiEYKLgoEVHTet7SzHQfzRTw1/cP26ISKOTXVvnNtKIPzfrAeV5Lf1K5VLIVvaZWxS/hJGCChnOBIUhEIirSMJDRRZa3ORMI4Q+a5d+z42MjOpsrgxgVhakhQuB9F5SsHrfjUDXaVjkB35XkJCSpM8sytXJk0vowQIxoVQIxEi7BTbTEjFuYuKYWiYop6xHCcThASfB5AhXs0WeXKRkFlkqh/R7pus3wCqjteg80KTZN0u3GhxIDNLhcGbFsrW1PS7anTLI0zVaP1zkv5IV3D3L2Ki9n2By5rGa2gywyxY5tSWlTRqgT4RVNV6xOLdXkSnAFXar3GM1nDsx2SBjj149KqPCJveXe9K0EU5FLQKQ46zdBvHYkRle78BdD8R9i1+BkTKEPpb+CPfm/jRyHezDWGoL/5pLMhllBdvsvjUV+qwYGQBlqSjILs9GGBZ2BeTyfOakryjR5IMeUDAHoWWoauKLhUQw8b4pNARHRRh7+LxfIY1aJR7w4mBAMlFZAks/5UD+kcnek/HJCUVnsQ4Y7akGeoHuOGgUUZSFrAV2Ff3tH7zyqX23ihuWPztn5xSOWRHaSnDLowObf+7q8= MIME-Version: 1.0

MIP SEGMENT STRUCTURE DID NOT CHANGE
Relink Process- perform the following steps to connect Microix to the new MIP database

 

 

 

 

MIP SEGMENT STRUCTURE CHANGED
In addition to the Relink Process, perform the steps below to configure Microix database to accept the new segment changes. (NOTE: if adding a new segment to MIP’s database, the segment will be required on all in process documents before transferring to MIP. All historical documents will have blank values for the new segment.)