升级至Agile Central 2017.1后Rally.data.wsapi.Model.Save()失效求助

Hey there! Let’s break down why your custom Rally app’s save method stopped working after upgrading to 2017.1, especially since it ran smoothly in 2016.2-1. Since you’re new to Rally app development, I’ll keep this straightforward and actionable:

Common Causes & Fixes #

1. Outdated WSAPI Version #

Rally 2017.1 introduced updates to its Web Services API (WSAPI). If your app is still targeting an older API version (like v2.0), this could break the save() method.

Check your app’s model configuration for a line like:

Rally.data.wsapi.Model.configure({ apiVersion: 'v2.0' });

Update it to match the 2017.1 compatible version (typically v2.1 or higher). You can confirm the correct version in Rally’s internal documentation for 2017.1.

2. Missing Error Handling (Critical for Debugging) #

You’re probably not seeing why the save is failing because the app isn’t capturing error details. Modify your save() call to include success/failure callbacks so you can debug the root cause:

// Example of a properly handled save call
myCostModel.save({
    // Your fields to update (e.g., Cost: 1500)
}, {
    success: function(savedRecord) {
        console.log('Save succeeded:', savedRecord.get('Name'));
    },
    failure: function(record, error) {
        // This will log the exact issue to your browser console
        console.error('Save failed:', error.message, error.errors);
    }
});

Check your browser’s developer console for these error messages—they’ll tell you if it’s a permission issue, missing required field, or deprecated field name.

3. Permission or Field Access Changes #

2017.1 might have adjusted permissions for portfolio-related artifacts (like Portfolio Items or Cost fields). Ensure:

• The user running the app has write permissions for the artifacts you’re trying to save.
• Any custom fields your app uses are still active and haven’t been renamed/deprecated in the 2017.1 environment.

4. Deprecated SDK Syntax #

Rally’s SDK sometimes changes method signatures between versions. If you were using an older way of calling save() (e.g., passing fields without an options object), this might no longer work.

Double-check the 2017.1 SDK docs for the correct Rally.data.wsapi.Model.save() syntax—make sure you’re passing the field data as the first argument and the options (success/failure callbacks) as the second.

5. Isolate the Issue with a Minimal Test App #

To rule out conflicts from other parts of your portfolio cost app, build a tiny test app that does one thing: fetch a single portfolio item model and try to save a small change. If this test app works, the problem is likely in how your main app is processing data or interacting with the model before calling save().

Next Steps #

Once you add the error handling, share the error messages you see in the console—that’ll help narrow down the exact issue even further. Don’t worry if it feels overwhelming at first; debugging Rally app version changes is super common, and those error logs are your best friend here!

内容的提问来源于stack exchange，提问作者Fire_Beard