-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Converting the Change Increment ID KB to devdocs #5129
Conversation
|
@dobooth did you check the topics with |
dshevtsov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General: The topics for 2.2 and 2.3 are identical. Is there a reason to not create a symlink?
Also, see my review comments to the changed files.
|
|
||
| 1. Find stores and entities for which the new increment ID should be changed. | ||
| 1. Connect to your MySQL DB. | ||
| For Magento Commerce (Cloud), at first, you need to SSH to your environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to SSH -> to connect using SSH
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace Magento Commerce (Cloud) with a variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dun and Dun
|
|
||
| ## Affected versions | ||
|
|
||
| - Magento Commerce (on premise): 2.x.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace Magento Commerce with a variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
| ## Affected versions | ||
|
|
||
| - Magento Commerce (on premise): 2.x.x | ||
| - Magento Commerce (Cloud): 2.x.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace Magento Commerce (Cloud) with a variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
|
||
| - Magento Commerce (on premise): 2.x.x | ||
| - Magento Commerce (Cloud): 2.x.x | ||
| - MySQL: any supported version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a link to the topic and section that lists supported versions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| ``` | ||
|
|
||
| {: .bs-callout-info} | ||
| Important: The new increment value must be greater than the current one, not less. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove , not less
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
|
|
||
| The next order placed at the store with `ID=1` will have the ID '#100002000'. | ||
|
|
||
| ## Additional recommended steps on production environments (cloud) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cloud -> Cloud
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't use cloud in parenthesis.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nobody puts baby in the corner.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😜
|
|
||
| ## Additional recommended steps on production environments (cloud) | ||
|
|
||
| Before executing the `ALTER TABLE` query on a production environment of Magento Commerce (Cloud), we strongly recommend performing these steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace Magento Commerce (Cloud) with a variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
|
|
||
| ## Affected versions | ||
|
|
||
| - Magento Commerce (on premise): 2.x.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace Magento Commerce with a variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| ## Affected versions | ||
|
|
||
| - Magento Commerce (on premise): 2.x.x | ||
| - Magento Commerce (Cloud): 2.x.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace Magento Commerce (Cloud) with a variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Converted.
|
|
||
| - Magento Commerce (on premise): 2.x.x | ||
| - Magento Commerce (Cloud): 2.x.x | ||
| - MySQL: any supported version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add a link to the topic that lists the supported versions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good.
|
|
||
| 1. Find stores and entities for which the new increment ID should be changed. | ||
| 1. Connect to your MySQL DB. | ||
| For Magento Commerce (Cloud), at first, you need to SSH to your environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Variable for Magento Commerce cloud is {{site.data.var.ece}}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
| - Some order records have been lost, but their IDs are already being used by payment gateways (like PayPal) for your current Merchant account. Such being the case, the payment gateways stop processing new orders that have the same IDs, returning the "Duplicate invoice id" error | ||
|
|
||
| {: .bs-callout-info} | ||
| You may also fix the payment gateway issue for PayPal by allowing multiple payments per invoice ID in PayPal's Payment Receiving Preferences. See the Knowledge Base article: [PayPal gateway rejected request - duplicate invoice issue][] . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| You may also fix the payment gateway issue for PayPal by allowing multiple payments per invoice ID in PayPal's Payment Receiving Preferences. See the Knowledge Base article: [PayPal gateway rejected request - duplicate invoice issue][] . | |
| You may also fix the payment gateway issue for PayPal by allowing multiple payments per invoice ID in PayPal's Payment Receiving Preferences. See [PayPal gateway rejected request - duplicate invoice issue][] in the _Knowledge Base_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed!
|
|
||
| ## Additional recommended steps on production environments (cloud) | ||
|
|
||
| Before executing the `ALTER TABLE` query on a production environment of Magento Commerce (Cloud), we strongly recommend performing these steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Variable for cloud...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup
| - Test the entire procedure of changing the increment ID on your Staging environment | ||
| - [Create a DB backup][] to restore your Production DB in case of failure | ||
|
|
||
| ## Related documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Boo...these related sections are draining and prone to URL maintenance. I would work links in to the content where it is relevant, or remove them completely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think they are ok.
|
|
||
| The next order placed at the store with `ID=1` will have the ID '#100002000'. | ||
|
|
||
| ## Additional recommended steps on production environments (cloud) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't use cloud in parenthesis.
| - Test the entire procedure of changing the increment ID on your Staging environment | ||
| - [Create a DB backup][] to restore your Production DB in case of failure | ||
|
|
||
| ## Related documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Boo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping it.
dobooth
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All points taken.
|
|
||
| ## Affected versions | ||
|
|
||
| - Magento Commerce (on premise): 2.x.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| ## Affected versions | ||
|
|
||
| - Magento Commerce (on premise): 2.x.x | ||
| - Magento Commerce (Cloud): 2.x.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Converted.
|
|
||
| - Magento Commerce (on premise): 2.x.x | ||
| - Magento Commerce (Cloud): 2.x.x | ||
| - MySQL: any supported version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good.
| - Some order records have been lost, but their IDs are already being used by payment gateways (like PayPal) for your current Merchant account. Such being the case, the payment gateways stop processing new orders that have the same IDs, returning the "Duplicate invoice id" error | ||
|
|
||
| {: .bs-callout-info} | ||
| You may also fix the payment gateway issue for PayPal by allowing multiple payments per invoice ID in PayPal's Payment Receiving Preferences. See the Knowledge Base article: [PayPal gateway rejected request - duplicate invoice issue][] . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed!
|
|
||
| 1. Find stores and entities for which the new increment ID should be changed. | ||
| 1. Connect to your MySQL DB. | ||
| For Magento Commerce (Cloud), at first, you need to SSH to your environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
| SHOW TABLE STATUS FROM `{database_name}` WHERE `name` LIKE 'sequence_{entity_type}_{store_id}'; | ||
| ``` | ||
|
|
||
| ## Example |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed them.
| ``` | ||
|
|
||
| {: .bs-callout-info} | ||
| Important: The new increment value must be greater than the current one, not less. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
|
|
||
| The next order placed at the store with `ID=1` will have the ID '#100002000'. | ||
|
|
||
| ## Additional recommended steps on production environments (cloud) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nobody puts baby in the corner.
|
|
||
| ## Additional recommended steps on production environments (cloud) | ||
|
|
||
| Before executing the `ALTER TABLE` query on a production environment of Magento Commerce (Cloud), we strongly recommend performing these steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
| - Test the entire procedure of changing the increment ID on your Staging environment | ||
| - [Create a DB backup][] to restore your Production DB in case of failure | ||
|
|
||
| ## Related documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping it.
|
|
Yes, because I couldn't get the symlink to work correctly. So I made a separate topic, which will go away soon enough. |
|
@dobooth what was the issue with symlink? |
|
'User error' I'm sure. |
|
running tests |
|
Hi @dobooth, thank you for your contribution! |
Purpose of this pull request
This pull request (PR) converts a KB article into a devdoc.
Affected DevDocs pages
whatsnew
Added the Change increment ID for a database entity on particular store topic to the Configuration Guide.