Timeline for Copy List Item and Keep Same ID
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2015 at 13:37 | comment | added | Paul Strupeikis | They won't void the warranty if you are doing CRUDs. The thing you can't do is change the db schema (tables, functions, procedures etc.). I don't see a problem with querying the database even 100 times a day. If one time is fine, a 100 times is fine as well :) | |
| Feb 10, 2015 at 13:25 | comment | added | luccio | 1. true, it is not recommended and can void warranty 2. MS has no chance to find out you are using some tool which is not deployed to server, but can check the WF/solution you have in your farm - there will be DB call, update -> bye bye warranty. Sure, the worst case scenario but I cannot recommend accessing the DB directly. This is not one-time migration, but WF which makes huge difference. | |
| Feb 10, 2015 at 13:05 | history | edited | Paul Strupeikis | CC BY-SA 3.0 |
added 542 characters in body
|
| Feb 10, 2015 at 11:31 | history | edited | Paul Strupeikis | CC BY-SA 3.0 |
added 2 characters in body
|
| Feb 10, 2015 at 11:25 | history | edited | Paul Strupeikis | CC BY-SA 3.0 |
added 2 characters in body
|
| Feb 10, 2015 at 11:07 | history | answered | Paul Strupeikis | CC BY-SA 3.0 |