admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-02-14 20:59:30 +00:00
parent 09f4aa50fb
commit 4acfba69b7
1 changed files with 3 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files

70
ayanova/devdocs/todo.txt
View File

@@ -16,86 +16,22 @@ todo: WHEN HAVE WORKORDER FORM customer popup notes need to pop pop pop, forgot
## SERVER MISC ITEMS
todo: test v8migrate on big somewhat shakey database
Joyce may have requested a copy from Scott see if it can export to my server here from her test station with latest v8 migrate
Exporting data to AyaNova server @ http://localhost:7575/api/v8/
Pre-release test 7.6.1-alpha.106
Compiling 16 Unit model categories
Compiling 28 Unit service types
Compiling 70 Workorder item types
Compiling 11 Regions
Compiling 7 Client groups
Compiling 18 Workorder categories
Compiling 103 Part categories
Compiling 3 Scheduleable user groups
Compiling 71 Dispatch zones
Compiling 10 User skills
Compiling 9 User certifications
Compiling 6 Client note types
Exporting customized Locales
Locale Custom English is customized [signature: 1339066135] exporting
Exporting 21 Users (step 1/2)
Exporting 193 Rates
Exporting 5 TaxCodes
Exporting 2 Contracts
Exporting 235 HeadOffices
Exporting 3671 Clients
Exporting 127 Vendors
Exporting 222 LoanItems
Exporting 2803 Parts
Exporting 29 Projects
Exporting 589 PurchaseOrders
Exporting 325 UnitModels
Exporting 9730 Units (step 1/2)
Exporting 9730 Units (step 2/2)
Exporting 21 Users (step 2/2)
Exporting all Memos
Exporting 9486 Service Workorders
DUPLICATE: 14854 - has duplicate ID, not exported
DUPLICATE: 14927 - has duplicate ID, not exported
DUPLICATE: 14955 - has duplicate ID, not exported
DUPLICATE: 17368 - has duplicate ID, not exported
Exporting 1616 ScheduleMarkers
ERROR, During operation:
Start ScheduleMarker export
************
Export failed with error:
V8:util:RootObjectToAyaType -> type Workorder is not coded yet
stack:
at AyaNova.PlugIn.V8.util.RootObjectToAyaType(RootObjectTypes rot, WorkorderTypes specificWoType) in c:\data\ayanova\source\Plugins\AyaNova.Plugin.V8\util.cs:line 466
at AyaNova.PlugIn.V8.V8.<ExportScheduleMarkers>d__4c9.MoveNext() in c:\data\ayanova\source\Plugins\AyaNova.Plugin.V8\V8.cs:line 2543
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at AyaNova.PlugIn.V8.V8.<DoExport>d__0.MoveNext() in c:\data\ayanova\source\Plugins\AyaNova.Plugin.V8\V8.cs:line 354
todo: encrypt test db data
todo: v8 migrate additions
Erase DB warning must be very distinctive like bright yellow and red with crossbones etc
Report sent *to* the new server upon fail or completion
stored in a location easily found like notes or attach or something on superuser account
(memo to superuser maybe??)
should send the entire contents of the output screen error or not as it will contain useful info like dupes not exported etc
Duplicate id not exported
found this in the wild with 4a database 4 workorders not exported due to this
message doesn't clearly say that number was exported already
is there a way to still export them?
it really is easy to obliterate a v8 db on export
maybe a pre-setting at the server end allowing migrate to take place where all users but su are locked out and it's reset upon completion successfully?
this would also be convenient to know biz actions are for migrate and use as a signalt to bypass rules etc
however it does erase all data as a first step so... hmmm...
maybe it is what it is (tm)?
it's only to protect people from themselves.
Is it possible to login during migrate to the v8 server?
Need a running count per item, we have the total at the start so it should show what item it is currently processing of that count like 50/1000 or something