Betabiz
Experienced User
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Error 0: Unexpected import error - Object reference not set to an instance of an object
Hi - Im trying a number of things to fix this. I am literally importing 2 fields. The company name (to update the existing card) and the card status. I had a similar problem importing inactive status to items in this file, which was fixed by MYOB running a script on the file. Is this something that could be done on the Card File? I managed to successfully import and update some of the cards, but not all, and there is no logical reason that I can see for this to not work. With the exception that these cards may have been set up by being imported from a 3rd party programImporting inventory items bulk update for inactive items
Hi I have a client who wants to make a large number of inventory items inactive. We have exported the items from AccountRight. We have opened the TXT file in Excel and the client has put a Y next to those he wants to make inactive. When I import these items and select the option to update existing data, about 2000 of these items wont update as there are sales on file for these items. We can mark them inactive individually through MYOB by selecting that "yes we know there are sales on file, and we're ok with that" but the import file just bounces the items. Is there any way around this? I know the client is not going to be happy that he has spent a significant amount of time doing a tidy up in excel, only for about 1/4 of the items he has marked, to not update. help! ThanksRe: Migration Error - Foreign key constraint name = FK_NZGSTReturnOptions_OutputTaxAccount
Thanks Gavin I had removed the value for the GST outputs adj box - so I added a new GST GL code, added that to the outputs adjustment in the GST return, optimised the file then tried the upgrade again ... and it worked!!! Appreciate your help - thank you740Views0likes0CommentsMigration Error - Foreign key constraint name = FK_NZGSTReturnOptions_OutputTaxAccount
Hi Am trying to upgrade a V19 AccountRight Standard file to 2023.2. Below is my log. The linking for the GST codes is all correct, there are no linked adjustment codes in the Prepare GST return. I dont know where else to look. Can anyone shed any light on this for me please? Unsuccessful: Migration failure Company File Name : C:\Users\User\AppData\Local\MYOB\Temp\company file name.MYO Start Time : 04/04/2023 16:27:26 PM End Time : 04/04/2023 4:30:19 PM Migration Warnings: - Warning1 : Inserting Constraints: A foreign key value cannot be inserted because a corresponding primary key value does not exist. [ Foreign key constraint name = FK_NZGSTReturnOptions_OutputTaxAccount ] Migration errors: Source : UpgradeUtility Method : Upgrade Error : (UpgradeException): Extra info : System.Data.SqlServerCe.SqlCeException (0x80004005): A foreign key value cannot be inserted because a corresponding primary key value does not exist. [ Foreign key constraint name = FK_NZGSTReturnOptions_OutputTaxAccount ] at System.Data.SqlServerCe.SqlCeCommand.ProcessResults(Int32 hr) at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommandText(IntPtr& pCursor, Boolean& isBaseTableCursor) at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommand(CommandBehavior behavior, String method, ResultSetOptions options) at System.Data.SqlServerCe.SqlCeCommand.ExecuteNonQuery() at AR.Common.Database.SQLTask.ExecuteSQL(String sqlScript, SqlCeCommand command) at AR.Common.Database.SQLTask.Execute() at AR.Common.Database.SqlCeFileWrapper.ExecuteScripts(IEnumerable`1 scripts) at MYOB.Huxley.UpgradeUtility.DbCeManager.InsertFkConstraints() at MYOB.Huxley.UpgradeUtility.UpgradeStepsToV1.DbInsertFKConstraintsUpgradeStep.ProcessStep() at MYOB.Huxley.UpgradeUtility.UpgradeStep.Process() at MYOB.Huxley.UpgradeUtility.UpgradeUtility.Upgrade() Unsuccessful upgrade!Solved794Views0likes2Comments