This commit is contained in:
2020-05-05 20:34:32 +00:00
parent adadd4b1b5
commit 2fbb279a22

View File

@@ -75,22 +75,10 @@ CURRENT ITEM:
TEST: Is my ef core relationship enough with just annotations and navigation properties or do I need to define shit further
- Test create, retrieve, cascade delete
Modify v8 export to export everything (at least teh wikiable and attachable and custom fieldable)
Uniquify NAMES: go through all and check which ones need to be uniquified by checking db schema of v7 or biz rules maybe
this is a v8 export plugin concern, not a RAVEN server concern
MIGRATE these deprecated things off of a USER object created just to host their stuff (user because only biz admin has full rights to user)
Put them in an INACTIVE, NO RIGHTS User with the following
Global - wiki, files -> User "V7_GLOBAL_WIKI_REPOSITORY"
Region - wiki, files -> User "V7_REGION_WIKI_REPOSITORY_regionnamehere" this is preliminary as there is a ton of other shit to import from region into various other areas but it has a wiki so that should be dealt with
TEST EXPORT BIG DATABASE WITH TONS OF ATTACHMENTS
Finish off the v8 test export then get the below shit done so can move to stage 3 ASAP
unhandled exception of type 'System.AggregateException' occurred in AyaNova.dll: 'One or more errors occurred.'
Inner exceptions found, see $exception in variables window for more details.
Innermost exception System.InvalidOperationException : 'WorkOrderItem.WorkOrderId' and 'WorkOrderItem.WorkorderId' are both mapped to column 'workorderid' in 'aworkorderitem' but are configured to use different data types ('bigint' and 'integer').
============================
todo: PLANNING workorder data and class and route structure:
@@ -102,38 +90,6 @@ todo: PLANNING workorder data and class and route structure:
Consider UI in this as well, will need to decide at least what is visible when
PLANNING Workorder templates
Keep as is or...? TTM!?
todo: locale keys for 22 objects brought in, some need renaming
//Client -> Customer (wiki, files, custom fields)
Contract (wiki, files, custom fields)
HeadOffice (wiki, files, custom fields)
LoanItem -> LoanUnit (to better reflect what it actually will be with new features)(wiki, files, custom fields)
Part (wiki, files, custom fields)
Uniquify (part number (required, main, dupe checked but not enforced :( )) and part name (optional, not dupe checked) both exist, how to import?)
Need to decide how to handle, default is to keep same, but we really need unique names..or do we??
Project Uniquify + (wiki, files, custom fields)
PurchaseOrder (wiki, files NO ASSIGNED DOCS, custom fields )
Unit (wiki, files, custom fields)
UnitModel (wiki, files, custom fields)
Vendor (wiki, files, custom fields)
Workorder (service type) -> WorkOrder (keeps name, Pascal cased) (WIKI, FILES)
WorkOrderItem (custom fields)
Workorder (Service type template) -> WorkOrderTemplate (wiki, files, custom fields)
Workorder (Quote type) -> Quote wiki, files,
QuoteItem ( custom fields)
Workorder (quote template) -> QuoteTemplate (wiki, files, custom fields)
workorder (PM type) -> PM wiki, files,
PMItems ( custom fields)
Workorder (pm template) -> PMTemplate (wiki, files, custom fields)
todo: PLANNING Look at attachment saving code on server, should it zip?
- pros and cons?
---------------------------------------------
todo: WIKI insert image should have extra linefeed before and after because it fails to show the image at all if it follows something like <br> even though it appears to be on the next line
@@ -150,11 +106,10 @@ Integration tests for stubbed out objects?
todo: EventLog Processor at server has TWO! separate skip and take portions in the same query, wtf?
todo: User get route is returning password, login and salt in UI explorer WTF?
todo: Can't hide custom fields on widget form? (no code to check if it's hidden?!)
- maybe because each individual field can be hidden in it so if they are all hidden then nothing shows?
some kind of funkiness when I was trying to make a widget on an empty db, couldn't save but was dirty.
- related to wiki changes or attachments or something?
- Might have fixed, re-test
Opening the widgets list on a new empty db I got this error at server:
2020-05-02 13:20:40.4589|ERROR|Server|Error=>System.ArgumentNullException: Value cannot be null. (Parameter 'AyaDataList:GetCustomFieldDefinitionsForList, Custom field object type Widget has no FormCustom defined')