Save FrameMaker 2020 to 2019 via ExtendScript bug

[frameexpert]

When I save a FrameMaker 2020 file down to FrameMaker 2019 using ExtendScript, the top line of the file still says <MakerFile 16.0> so it won't open in 2019. It works in the interface with File > Save As.

#target framemaker

var doc;

doc = app.ActiveDoc;
saveDoc (doc);
doc.Close (true);

function saveDoc (doc) {	
    
    var params, returnParams, i;
    
    params = GetSaveDefaultParams ();
    returnParams = new PropVals ();

    i = GetPropIndex (params, Constants.FS_FileType);
    params[i].propVal.ival = Constants.FV_SaveFmtBinary150;
    i = GetPropIndex (params, Constants.FS_AutoBackupOnSave);
    params[i].propVal.ival = Constants.FV_SaveNoAutoBackup;
    i = GetPropIndex (params, Constants.FS_FileIsInUse);
    params[i].propVal.ival = Constants.FV_ResetLockAndContinue;

	FA_errno = 0;
    doc.Save (doc.Name, params, returnParams);
    if (FA_errno !== 0) {
		PrintSaveStatus (returnParams);
	}
}

[Winfried Reng]

Hi Rick,

It seems that this is an old bug:

https://tracker.adobe.com/#/view/FRMAKER-5258

When you vote there, it might get more attention.

Best regards

Winfried

[Klaus Göbel]

It's different from this bug. This old bug made the document unreadable. This new bug only pretends to save as 2019, but it stays 2020

[Amitojsingh]

Kindly log a new bug for the same.

[Jason L-S]

Any idea when this will be fixed?

I found a bug report here:

FRMAKER-9560 | Tracker (adobe.com)

But it's been closed as "Duplicate". I can't find the duplicate.

[Ian Proudfoot]

Is this the duplicate: FRMAKER-9526 ?

It is showing as fixed 

[Jason L-S]

Yes that appears to be the duplicate. Looks like it was fixed in build 16.0.2.834. Thanks!