Gsyfuy

Advice for a new journal editor

Describing what the world looks like in UV and IR

If I delete my router's history can my ISP still provide it to my parents?

How do you funnel food off a cutting board?

What would the chemical name be for C13H8Cl3NO

Can a long polymer chain interact with itself via van der Waals forces?

Why did the villain in the first Men in Black movie care about Earth's Cockroaches?

Early credit roll before the end of the film

What is the wife of a henpecked husband called?

Nested word series [humans only]

Can a hotel cancel a confirmed reservation?

Bash Script Function Return True-False

Does theoretical physics suggest that gravity is the exchange of gravitons or deformation/bending of spacetime?

How does Leonard in "Memento" remember reading and writing?

Why is working on the same position for more than 15 years not a red flag?

Why is Agricola named as such?

How can my powered armor quickly replace its ceramic plates?

A title for a history book

Why was Lupin comfortable with saying Voldemort's name?

What are career options for big-picture thinkers with no experience?

Eww, those bytes are gross

Why zero tolerance on nudity in space?

Intern applicant asking for compensation equivalent to that of permanent employee

What is the most fuel efficient way out of the Solar System?

Magento Recommended way to add comment to order

Best practice to add a layout handle for my custom module?Recommended way to Install Magento 2 on shared hosting, Composer or archivesMagento 2: How to programatically check if an order exists without using try-catch?List of filters for sales order APIWhen Should We Use a Repository and Factory in Magento 2?Return order details in REST API Magento-2Magento 1.9 API Performance - Retrieving All Sales Order InfoMagento 2 REST API - Add Order CommentMagento2: searching for orders through REST is too slow.Magento 2.3 - Preserving Success message for show

0

I am looking for the Magento recommended best practice for adding a comment to an order. I can easily accomplish this using things such as $order->addCommentToStatusHistory($message)->save() and similar actions. However I know that using a direct save action is not recommended on models and you should instead us managers/repositories.

I have also found that there is a MagentoSalesApiOrderStatusHistoryRepositoryInterface now which provides the save function. So what I'm trying to figure out is how to approach this properly. This is my best guess.

private $orderStatusHistoryRepository;



public function __construct(

    MagentoSalesApiOrderStatusHistoryRepositoryInterface $orderStatusHistoryRepository

) {

    $this->orderStatusHistoryRepository = $orderStatusHistoryRepository;

}



public function myFunction(MagentoSalesApiDataOrderInterface $order)

{

    //... additional logic here

    $history = $order->addCommentToStatusHistory($message);

    $this->orderStatusHistoryRepository->save($history);

}

What I'm not certain about is if this is the proper approach AND should I also be saving the order using OrderRepositoryInterface, or if that is unnecessary.

I have looked through a lot of questions and answers around this as well as looking through some tutorials and documentation. However all of these provide conflicting information and most of them recommend ways that I know are not Magento best practice.

If there is documentation out there that would answer my question and I have overlooked it please point me in the right direction.

This is for Magento 2.3.0.

magento2 sales-order magento2.3 best-practice order-comment

share

asked 8 mins ago

rain2orain2o

1816

add a comment | 

0

I am looking for the Magento recommended best practice for adding a comment to an order. I can easily accomplish this using things such as $order->addCommentToStatusHistory($message)->save() and similar actions. However I know that using a direct save action is not recommended on models and you should instead us managers/repositories.

I have also found that there is a MagentoSalesApiOrderStatusHistoryRepositoryInterface now which provides the save function. So what I'm trying to figure out is how to approach this properly. This is my best guess.

private $orderStatusHistoryRepository;



public function __construct(

    MagentoSalesApiOrderStatusHistoryRepositoryInterface $orderStatusHistoryRepository

) {

    $this->orderStatusHistoryRepository = $orderStatusHistoryRepository;

}



public function myFunction(MagentoSalesApiDataOrderInterface $order)

{

    //... additional logic here

    $history = $order->addCommentToStatusHistory($message);

    $this->orderStatusHistoryRepository->save($history);

}

What I'm not certain about is if this is the proper approach AND should I also be saving the order using OrderRepositoryInterface, or if that is unnecessary.

I have looked through a lot of questions and answers around this as well as looking through some tutorials and documentation. However all of these provide conflicting information and most of them recommend ways that I know are not Magento best practice.

If there is documentation out there that would answer my question and I have overlooked it please point me in the right direction.

This is for Magento 2.3.0.

magento2 sales-order magento2.3 best-practice order-comment

share

asked 8 mins ago

rain2orain2o

1816

add a comment | 

I am looking for the Magento recommended best practice for adding a comment to an order. I can easily accomplish this using things such as $order->addCommentToStatusHistory($message)->save() and similar actions. However I know that using a direct save action is not recommended on models and you should instead us managers/repositories.

I have also found that there is a MagentoSalesApiOrderStatusHistoryRepositoryInterface now which provides the save function. So what I'm trying to figure out is how to approach this properly. This is my best guess.

private $orderStatusHistoryRepository;



public function __construct(

    MagentoSalesApiOrderStatusHistoryRepositoryInterface $orderStatusHistoryRepository

) {

    $this->orderStatusHistoryRepository = $orderStatusHistoryRepository;

}



public function myFunction(MagentoSalesApiDataOrderInterface $order)

{

    //... additional logic here

    $history = $order->addCommentToStatusHistory($message);

    $this->orderStatusHistoryRepository->save($history);

}

What I'm not certain about is if this is the proper approach AND should I also be saving the order using OrderRepositoryInterface, or if that is unnecessary.

I have looked through a lot of questions and answers around this as well as looking through some tutorials and documentation. However all of these provide conflicting information and most of them recommend ways that I know are not Magento best practice.

If there is documentation out there that would answer my question and I have overlooked it please point me in the right direction.

This is for Magento 2.3.0.

magento2 sales-order magento2.3 best-practice order-comment

share

asked 8 mins ago

rain2orain2o

1816

private $orderStatusHistoryRepository;



public function __construct(

    MagentoSalesApiOrderStatusHistoryRepositoryInterface $orderStatusHistoryRepository

) {

    $this->orderStatusHistoryRepository = $orderStatusHistoryRepository;

}



public function myFunction(MagentoSalesApiDataOrderInterface $order)

{

    //... additional logic here

    $history = $order->addCommentToStatusHistory($message);

    $this->orderStatusHistoryRepository->save($history);

}

share

asked 8 mins ago

rain2orain2o

1816

share

asked 8 mins ago

rain2orain2o

1816

asked 8 mins ago

rain2orain2o

1816

asked 8 mins ago

rain2orain2o

1816