help.mvpone.com Open in urlscan Pro
54.204.238.15  Public Scan

Form analysis
4 forms found in the DOM

POST /questions

<form accept-charset="UTF-8" action="/questions" class="form floating-labels" id="new_question" method="post">
  <fieldset>
    <p>Please fill out the contact form below and we will reply as soon as possible.</p>
    <!-- Don't modify or delete this below -->
    <input type="hidden" value="9394" name="question[account_id]" id="question_account_id">
    <input placeholder="Your email" class="field email" type="email" name="question[email]" id="question_email" required="">
    <input placeholder="Your question" type="text" class="field message" name="question[name]" id="question_name" required="">
    <textarea placeholder="Description (details)" class="field message" type="text" name="question[description]" id="question_description"></textarea>
    <div><input type="submit" id="question_submit" name="commit" value="Contact Support" class="button"></div>
  </fieldset>
</form>

POST /questions

<form accept-charset="UTF-8" action="/questions" class="form floating-labels" id="new_question" method="post">
  <fieldset>
    <p>Please fill out the contact form below and we will reply as soon as possible.</p>
    <!-- Don't modify or delete this below -->
    <input type="hidden" value="9394" name="question[account_id]" id="question_account_id">
    <input placeholder="Your email" class="field email" type="email" name="question[email]" id="question_email" required="">
    <input placeholder="Your question" type="text" class="field message" name="question[name]" id="question_name" required="">
    <textarea placeholder="Description (details)" class="field message" type="text" name="question[description]" id="question_description"></textarea>
    <div><input type="submit" id="question_submit" name="commit" value="Contact Support" class="button"></div>
  </fieldset>
</form>

POST /questions/2516097/feedbacks

<form accept-charset="UTF-8" action="/questions/2516097/feedbacks" class="new_feedback" id="new_feedback" method="post">
  <input name="authenticity_token" type="hidden" value="W7fIKyhlMGSYY6ZpNZ0EjAuXfvwpXGjx8KK7p9liJk0=" style="display: none">
  <input id="feedback_score" name="feedback[score]" type="hidden" value="0" style="display: none">
  <a id="yes" class="response feedback">
                            <div class="thumb-up">
                                <i class="far fa-thumbs-up"></i>
                                <span>Yes</span>
                            </div>
                        </a>
  <a id="no" class="response feedback">
                            <div class="thumb-down">
                                <i class="far fa-thumbs-down"></i>
                                <span>No</span>
                            </div>
                        </a>
</form>

POST /admin/feedbacks/comments

<form data-action="submit->feedbacks#submitForm" class="new_feedback_comment" id="new_feedback_comment" action="/admin/feedbacks/comments" accept-charset="UTF-8" data-remote="true" method="post">
  <input type="hidden" name="authenticity_token" id="authenticity_token" value="qF_z0hHs5iG5mzX6-OeIeNg5rKWpQe2HDXDOgXT7vjo5gR3R_Z75pNbPqE2esRVcSnznhgvG_1Qvt37380APlA" autocomplete="off">
  <h3>How can we improve this article?</h3>
  <button id="close-feedback-form" data-action="click->feedbacks#hideFeedbackForm"><i class="far fa-times"></i></button>
  <input value="2516097" autocomplete="off" type="hidden" name="feedback_comment[question_id]" id="feedback_comment_question_id">
  <input value="" data-feedbacks-target="selectedText" autocomplete="off" type="hidden" name="feedback_comment[excerpt]" id="feedback_comment_excerpt">
  <div class="field">
    <input data-feedbacks-target="feedbackOption" required="required" type="radio" value="inaccurate" name="feedback_comment[kind]" id="feedback_comment_kind_inaccurate">
    <label for="feedback_comment_kind_inaccurate">Inaccurate - doesn't match what I see in the product</label>
  </div>
  <div class="field">
    <input data-feedbacks-target="feedbackOption" required="required" type="radio" value="hard_to_understand" name="feedback_comment[kind]" id="feedback_comment_kind_hard_to_understand">
    <label for="feedback_comment_kind_hard_to_understand">Hard to Understand - unclear or translation is wrong</label>
  </div>
  <div class="field">
    <input data-feedbacks-target="feedbackOption" required="required" type="radio" value="missing_info" name="feedback_comment[kind]" id="feedback_comment_kind_missing_info">
    <label for="feedback_comment_kind_missing_info">Missing info - relevant but not comprehensive</label>
  </div>
  <div class="field">
    <input data-feedbacks-target="feedbackOption" required="required" type="radio" value="irrelevant" name="feedback_comment[kind]" id="feedback_comment_kind_irrelevant">
    <label for="feedback_comment_kind_irrelevant">Irrelevant - doesn’t match the title and / or my expectations</label>
  </div>
  <div class="field">
    <input data-feedbacks-target="feedbackOption" required="required" type="radio" value="minor_errors" name="feedback_comment[kind]" id="feedback_comment_kind_minor_errors">
    <label for="feedback_comment_kind_minor_errors">Minor errors - formatting issues, typos, and / or broken links</label>
  </div>
  <div class="field">
    <input data-feedbacks-target="feedbackOption" required="required" type="radio" value="other" name="feedback_comment[kind]" id="feedback_comment_kind_other">
    <label for="feedback_comment_kind_other">Other</label>
  </div>
  <h3 class="additional-info">Share additional info and suggestions</h3>
  <div class="field">
    <textarea placeholder="Additional Comments" data-feedbacks-target="additionalReview" name="feedback_comment[comment]" id="feedback_comment_comment" cols="1" rows="5"></textarea>
  </div>
  <div class="field email">
    <input name="feedback_comment[notify_about_changes]" type="hidden" value="0" autocomplete="off"><input id="notify-about-feedback-changes" data-feedbacks-target="notifyIcon" data-action="change->feedbacks#toggleEmail" type="checkbox" value="1"
      name="feedback_comment[notify_about_changes]">
    <label for="notify-about-feedback-changes">Notify me about changes</label>
    <input placeholder="Your Email" data-feedbacks-target="notifyEmail" type="email" name="feedback_comment[email]" id="feedback_comment_email" style="display: none;">
  </div>
  <div class="field actions">
    <input type="submit" name="commit" value="Submit" data-feedbacks-target="submitButton" data-disable-with="Submit" disabled="disabled">
    <button class="cancel-feedback" data-action="click->feedbacks#hideFeedbackForm">Cancel</button>
  </div>
</form>

Text Content

English (US)
US English (US)
FR French
DE German
MX Spanish (Mexico)


CONTACT US

If you still have questions or prefer to get help directly from an agent, please
submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.


 * Contact Us

 * Home
 * Inventory
 * Parts


PARTS MERGE

Learn how to seamlessly merge different parts to create a cohesive whole in your
creative projects with innovative techniques and tips.


CONTACT US

If you still have questions or prefer to get help directly from an agent, please
submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.


 * Getting Started
   Users and Reports Assets and Work Inventory and Purchasing
 * Accounting
   Accounts Cost Centers Departments Expense Classes
 * Administration
   General Work Purchasing Assets Inventory Users Email Mobile Errors PLC Import
   Wizard Browser Webinars Release Notes Database Reporting Licensing People
 * Alerts
 * Assets
   General Asset Tree Availability Financials Meters Repairable Spares Spare
   Parts Lists
 * Dashboard and Widgets
 * Enterprise
 * Inventory
   General Parts Cycle Counts Tools Vendors Warehouses & Stock Locations
 * Mobile CMMS
   Android iOS
 * On-Premises
 * People
   Requestors Customers
 * Purchasing
   Purchase Orders Purchase Requests Approval Blanket Purchase Orders Receiving
   Shipping Vendors
 * Reporting
   Adminstration Accounting Assets Export/Import Inventory People Purchasing
   Work
 * Work
   Work Orders PMs Work Request Work Groups PdMs Job Plans Instructions
   Scheduling Projects
 * MVP Tips of the Month
   TOTM-2022 TOTM-2023 TOTM-2024

+ More

The Parts Merge action will allow you to combine two part records, while
selecting what information from each record you want to keep. This will allow
you to keep one of those Part records, while deleting the other from your
database. 

This action can be useful if you have duplicate records created for the same
part. This merge will maintain the historical information of the part, while
allowing you to clean up your digital inventory. 

Potential duplicate Parts in your database can be found by running the Duplicate
Parts report under My Reports> Inventory. 

 

Steps to Merge Parts

Selecting Parts

Select one Part and use Action > Merge to begin the Parts Merge process.



Click to Zoom



This will open up the Parts Merge menu and allow you to select a second part to
combine with. If the grey down arrow next to the secondary Part ID field is
selected, it will populate recommended potential duplicates. These
recommendations are based on parts that have similar Descriptions, Part Types,
Part Classes, MFR Part IDs, and Vendor Part IDs. 



Click to Zoom



OR

Those users with access to Batch Edit can select two Parts using the checkboxes
on the left hand side of the page. Then select Action> Merge.



Click to Zoom



This will open up the Parts Merge menu with both part records displayed.



Click to Zoom



 

Merging Parts

Once multiple parts have been selected, users can select the Primary Record and
the Part ID that will remain. Please note that the Part ID that is not selected
will be deleted permanently. However, all Part and Transaction history will be
kept in the Primary record. 

As can be seen in the image below, field values can be selected from either Part
record. This will save those values and bring them over to the Primary Record
once the Merge is completed. Therefore in this example, the values for Weight
and Part Class will be saved and merged to the Primary Record. All other values
will remain the same in the Primary record, since the boxes for those fields are
selected. 

Select OK to complete the Parts Merge. 



Click to Zoom



If the Non-Primary Part Record has any Stock Information the following message
will appear notifying the User. 



Click to Zoom



This notification is designed to notify Users and allow them to physically move
the Parts in the Stockroom of their facility, or manually adjust the MVP Stock
information before the Merge is completed. After the Merge, Stock Information
will be moved over to the Primary Part. If the non-primary part and the primary
part have stock in the same Warehouse and Stock Location, their QTY will be
combined.

Please note that when a part is merged the following information will update and
merge together into the Primary Part ID:

 * Any selected Part fields
 * Historical Part Transactions
 * Stock Information
 * Replenishment Information
 * Part Substitutes
 * Spare Part List Information
 * Purchasing Information
 * Estimated Part Information
 * Part List Information 
 * Navigation History

Parts Merge was added in the Summer 2024 release. To enable this powerful
feature for your team, have an MVP One admin add it to specific roles today.
Contact our Technical Support Team to get started!

 

 

 

 

Was this article helpful?

Yes
No


HOW CAN WE IMPROVE THIS ARTICLE?

Inaccurate - doesn't match what I see in the product
Hard to Understand - unclear or translation is wrong
Missing info - relevant but not comprehensive
Irrelevant - doesn’t match the title and / or my expectations
Minor errors - formatting issues, typos, and / or broken links
Other


SHARE ADDITIONAL INFO AND SUGGESTIONS


Notify me about changes
Cancel


RELATED ARTICLES

 * Blanket PO Receiving
 * Cannot Process Part Return Due to No Quantity to Return
 * Part Return

Copyright 2024 – MVP.

Knowledge Base Software by Helpjuice

Knowledge Base Software powered by Helpjuice

DEFINITION BY AUTHOR

0
0
Close Expand


LEARN HOW TO SEAMLESSLY MERGE DIFFERENT PARTS TO CREATE A COHESIVE WHOLE IN YOUR
CREATIVE PROJECTS WITH INNOVATIVE TECHNIQUES AND TIPS.