Timeline for Bypassing schema lock for a join on a feature class published to service?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2016 at 18:25 | comment | added | Midavalo♦ | @GeoffreyWest please edit your question to include the extra info that you are wanting the join to modify the schema | |
| Oct 3, 2016 at 18:14 | comment | added | Midavalo♦ | @GeoffreyWest I have updated my answer | |
| Oct 3, 2016 at 18:13 | history | edited | Midavalo♦ | CC BY-SA 3.0 |
included note about schema locking
|
| Oct 3, 2016 at 18:08 | comment | added | Geoffrey West | I am aware; this is the desired output, I have tested this with the service being turned off and it works correctly; I just need to modify the feature class while the service is turned on. | |
| Oct 3, 2016 at 18:06 | comment | added | Midavalo♦ | By permanently modify the feature class I mean it actually adds all the fields from the join table. It doesn't just update existing fields. | |
| Oct 3, 2016 at 18:04 | comment | added | Geoffrey West | This is a standalone script; I am using a layer or table view which are acceptable data types for AddJoin, I would like to permanently change the feature class, so that is not the issue. | |
| Oct 3, 2016 at 18:00 | history | answered | Midavalo♦ | CC BY-SA 3.0 |