Notes
1. As with all updates that you make directly to the tables in Microsoft SQL Server Management Studio, have a current backup or test first in a copy of the database.
You assume all responsibility for any data updated by using SQL statements. If data becomes corrupted or inconsistent because of incorrectly updating records in SQL, Microsoft Customer Support Services will be unable to help with correcting the data.
2. There is no audit of these changes and they are not filtered by program logic so there is a risk in updating tables directly.
3. Typically you would have to roll the data back to a point when the tables and existing data is in sync. On rare occasion you may have to roll it forward.
4. Except on rare occasions, you would not change a record that is already released.
5. Do a Select statement first so that you know which records will be updated. Then use the same "where clause" with the update so that only those records will be updated.
6. Using "Begin tran" enables the update to be either Committed or Rolled Back. For example:
Begin tran
Update Batch set crtot = 111.22 where module = 'GL' and batnbr = '123456'
Now test to see how the data looks.
Select crtot ,* from batch where module = 'GL' and batnbr = '123456'
If you approve of the change, then enter and run:
COMMIT
If you do not approve and want to roll back the change, enter and run:
ROLLBACK
Steps:
1. Always have a current backup before you make updates in Management Studio.
2. Try to release the batch again in the Module>Release Batches screen as sometimes the batch will release without updating anything in SQL.
3. Use the worksheet information to help in updating incorrect fields so that all tables are in sync for a particular point in the processing of the batch.
4. Try to release the batch again in the Module>Release Batches screen.
5. If the batch does not release, run the debug for that module and contact Dynamics SL support for more help.