Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Conversation

@dobooth
Copy link
Contributor

@dobooth dobooth commented Aug 6, 2019

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.

@dobooth dobooth added 2.2.x 2.3.x Magento 2.3 related changes New Topic A major update published as an entirely new document labels Aug 6, 2019
@dobooth dobooth self-assigned this Aug 6, 2019
@dobooth dobooth changed the title Db kb conversion Converting the Change Increment Id KB to devdocs Aug 6, 2019
@dobooth dobooth requested a review from dshevtsov August 7, 2019 16:29
@dobooth dobooth changed the title Converting the Change Increment Id KB to devdocs Converting the Change Increment ID KB to devdocs Aug 7, 2019
@dshevtsov
Copy link
Collaborator

@dobooth did you check the topics with rake check?

Copy link
Collaborator

@dshevtsov dshevtsov left a 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.
Copy link
Collaborator

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

Copy link
Collaborator

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

Copy link
Contributor Author

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
Copy link
Collaborator

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

Copy link
Contributor Author

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
Copy link
Collaborator

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

Copy link
Contributor Author

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
Copy link
Collaborator

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

Copy link
Contributor Author

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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove , not less

Copy link
Contributor Author

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)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cloud -> Cloud

Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Contributor

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:
Copy link
Collaborator

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

Copy link
Contributor Author

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
Copy link
Collaborator

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

Copy link
Contributor Author

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
Copy link
Collaborator

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

Copy link
Contributor Author

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
Copy link
Collaborator

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

Copy link
Contributor Author

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.
Copy link
Contributor

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}}

Copy link
Contributor Author

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][] .
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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_.

Copy link
Contributor Author

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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Variable for cloud...

Copy link
Contributor Author

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
Copy link
Contributor

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.

Copy link
Contributor Author

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)
Copy link
Contributor

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Boo

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keeping it.

Copy link
Contributor Author

@dobooth dobooth left a 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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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][] .
Copy link
Contributor Author

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.
Copy link
Contributor Author

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
Copy link
Contributor Author

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.
Copy link
Contributor Author

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)
Copy link
Contributor Author

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:
Copy link
Contributor Author

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
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keeping it.

@dobooth dobooth requested a review from hguthrie August 12, 2019 15:44
@dobooth dobooth requested a review from dshevtsov August 12, 2019 15:44
@dshevtsov
Copy link
Collaborator

General: The topics for 2.2 and 2.3 are identical. Is there a reason to not create a symlink?

@dobooth
Copy link
Contributor Author

dobooth commented Aug 12, 2019

Yes, because I couldn't get the symlink to work correctly. So I made a separate topic, which will go away soon enough.

@dshevtsov
Copy link
Collaborator

@dobooth what was the issue with symlink?

@dobooth
Copy link
Contributor Author

dobooth commented Aug 13, 2019

'User error' I'm sure.

@dobooth
Copy link
Contributor Author

dobooth commented Aug 15, 2019

running tests

@dobooth dobooth merged commit 72793ad into master Aug 15, 2019
@ghost
Copy link

ghost commented Aug 15, 2019

Hi @dobooth, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@dobooth dobooth deleted the db_kb_conversion branch August 15, 2019 20:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

2.2.x 2.3.x Magento 2.3 related changes New Topic A major update published as an entirely new document

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants