Allow user to change the account of a record in the "account" drop down

Thanks for the additional context Casey. Adding a comment that I shared on a linked ticket:

Any solution we come up with will need to have some limitations placed on it as the data structure and data rules for any given account are quite specific to the account style that it belongs to. The main limitation will likely be that if we allow records to be moved from one account to another, the account style will need to be the same otherwise we cannot guarantee that the data will map to identical fields. We will also need to consider how this impacts the audit information (this is probably the trickiest part).

So moving data from one account to another (as long as they use the same account style) can likely be supported. Moving data from one account to another account using a different account style likely cannot be supported in the UI and would require extracting the data and reloading it via one of the templates.

Just as a note on best practice when accounts change suppliers, ideally the old account should be closed off (by setting a replaced on date) and updating the name to something like AccountNumber_CLOSED to avoid confusion with the new account. This will insure that the audit history is clearly maintained. One of the biggest challenges with moving data from one account to another will be to maintain a clear audit trail.

Hello, 

This can happen for a number of reasons beyond an automatic data loading process, so having the functionality would be extremely helpful within the platform. 

As one example, say we have data being manually uploaded. Imagine that we switched providers, but a new account hadn't been created for that data yet (users don't always think to notify an admin when there is a provider or meter change). An admin could then create the appropriate account and move anything that was uploaded in "wrong" account to the newly made correct account. 

To address the point of data loading, yes, there are many issues with that in and of itself. To name a few instances, these issues primarily happen when we have multiple sites on the same invoice, multiple sites using the same provider, and/or one site using the same provider for multiple commodities with different invoices. We have been working with Urjanet for months on this problem that impacts many of our sites with no fixes yet. In the meantime, and in case this never completely resolves, being able to move records from one account to another will help us utilize the envizi system more effectively and reduce the amount of rework and potential for error when having to delete records and accounts and creating a new record in the correct account. We are hoping PLUG will resolve these issues, but we want to be prepared and realistic if it doesn't. 

Hi Casey -- I will note this as a potential future consideration when we make updates to our UI but this is unlikely to be something we action soon. Having an invoice loaded into the wrong account is indicative of a problem with a connector or with the naming convention of the accounts or similar configuration issue. There are also challenges in enabling the ability to move a record to a different account as the account style, subtype settings, etc. could all be different between any two accounts meaning that a record cannot simply be moved to a different account without corrupting the content.

Either way it sounds like a process issue that should be fixed at the source rather than providing a quicker way to fix individual occurrences. If this is happening regularly for you then I suggest reaching out to support for assistance in addressing this issue.

Hi Michael,

This is when data is already loaded and is sometimes be caused by an invoice/data going into the wrong account. Regardless of how or what happens for that invoice and data to be in the wrong account, what we want to be able to do is easily move the record with the invoice to the correct account.

Today, we must download the invoice, delete the record, go to the correct account, create a record and add the invoice when it would be far better for the user to be able to simply change the account (which is why I highlighted the account field as an example of where to put it, but even if it becomes a right click drop-down selection, that would work great as well -- just like if you want to move an account to a different site. That's exactly what we want to do, but at the record level).

I moved this idea to a high priority as it has caused a lot of issues for our company by creating a lot of rework, which slows down what we are able to do.

Hi there -- can you please explain in more detail a scenario where this is required? This sounds more like an issue that should be addressed in the data loading process. If you have a specific case where this is happening can you please raise it as a support request.