Document custom properties are not saved in Word desktopDocument custom properties not save in Office 365 for WindowsAutomatically loading Word Task Pane Office Add-inDynamic data manipulation in word onlinecontext.document.saved property is prematurely updated even before the document is saved to SharePointWord Add-in - How to read custom document propertySave before closing a documentOffice 365 Word Add-In : Forbidden 403 when trying to create a document with the office javascript libraryRetrivig ID of Office 365 word document saved in sharepointDocument custom properties not save in Office 365 for WindowsCustom properties are not being saved immediately to Exchange Server in Outlook desktop 2016Bug with getFileAsync() method on word desktop

How can a function with a hole (removable discontinuity) equal a function with no hole?

Tiptoe or tiphoof? Adjusting words to better fit fantasy races

Did Dumbledore lie to Harry about how long he had James Potter's invisibility cloak when he was examining it? If so, why?

Increase performance creating Mandelbrot set in python

System.debug(JSON.Serialize(o)) Not longer shows full string

Closest Prime Number

Unexpected indention in bibliography items (beamer)

What is the difference between "behavior" and "behaviour"?

Flag only first row where condition is met in a DataFrame

How to escape string to filename? It is in backup a file append date

How to be diplomatic in refusing to write code that breaches the privacy of our users

How does Loki do this?

Was Spock the First Vulcan in Starfleet?

How do scammers retract money, while you can’t?

Is there any reason not to eat food that's been dropped on the surface of the moon?

How did Arya survive the stabbing?

Is a stroke of luck acceptable after a series of unfavorable events?

Is there a good way to store credentials outside of a password manager?

Is `x >> pure y` equivalent to `liftM (const y) x`

How can I get through very long and very dry, but also very useful technical documents when learning a new tool?

Is it okay for two “sein” to be next to each other?

How can I kill an app using Terminal?

What is the opposite of 'gravitas'?

Is the destination of a commercial flight important for the pilot?



Document custom properties are not saved in Word desktop


Document custom properties not save in Office 365 for WindowsAutomatically loading Word Task Pane Office Add-inDynamic data manipulation in word onlinecontext.document.saved property is prematurely updated even before the document is saved to SharePointWord Add-in - How to read custom document propertySave before closing a documentOffice 365 Word Add-In : Forbidden 403 when trying to create a document with the office javascript libraryRetrivig ID of Office 365 word document saved in sharepointDocument custom properties not save in Office 365 for WindowsCustom properties are not being saved immediately to Exchange Server in Outlook desktop 2016Bug with getFileAsync() method on word desktop













0















My office js Word add-in code saves a custom property to the document customproperty collection. The code for saving is as below.



Word.run(function (context) 
//method accepts property name plus value
context.document.properties.customProperties.add(propertyname, value);
context.document.save();
return context.sync()
.then(function ()
console.log("Property saved");
)
.catch (function (e)
console.log("Error occured inserting property " + e.message);

);
);


After my add-in executes I can see the custom property when I click on Info->Properties->AdvancedProperties->Custom. But when i close the Office 365 Word desktop application and reopen the document I find the custom property has not been saved. So I opened the Word document again in desktop and then again ran my add-in. This time I also typed some characters in the document and then closed the document. Now when I reopened the document I found that the custom properties are saved correctly. This means that custom properties are not getting saved when we execute the word context sync operation.



I then performed the same operation in Office online and it worked perfectly. This means that this issue occurs only in Office 365 Word Desktop. I had faced the same issue in Aug 2018. But it looks like the bug still exists.



I am running Word desktop Version 1808 (Build 10730.20304 Click-to-Run)










share|improve this question
























  • I tried to reproduce. If I save the Word document, the custom property is saved. If I close the Word document without saving, the property is not saved. But that's what I'd expect. Word Online has an autosave feature, so that's probably why it works there without explicitly saving.

    – Rick Kirkham
    Mar 21 at 16:35











  • I modified the code to include context.document.save(); But even then the custom properties are not saved. Even Word desktop has an autosave feature. This is not a feature but a bug.

    – Codecrasher99
    Mar 22 at 6:43











  • I can't reproduce. The bug that's referred to in your Aug 2018 question is about an unneeded prompt to save. But that is not your symptoms.

    – Rick Kirkham
    Mar 22 at 7:44











  • You mentioned that this happened in Aug 2018 - have you updated your Office since/

    – Mavi Domates
    Mar 22 at 8:25











  • Yes my office version has been updated since then.

    – Codecrasher99
    Mar 22 at 8:37















0















My office js Word add-in code saves a custom property to the document customproperty collection. The code for saving is as below.



Word.run(function (context) 
//method accepts property name plus value
context.document.properties.customProperties.add(propertyname, value);
context.document.save();
return context.sync()
.then(function ()
console.log("Property saved");
)
.catch (function (e)
console.log("Error occured inserting property " + e.message);

);
);


After my add-in executes I can see the custom property when I click on Info->Properties->AdvancedProperties->Custom. But when i close the Office 365 Word desktop application and reopen the document I find the custom property has not been saved. So I opened the Word document again in desktop and then again ran my add-in. This time I also typed some characters in the document and then closed the document. Now when I reopened the document I found that the custom properties are saved correctly. This means that custom properties are not getting saved when we execute the word context sync operation.



I then performed the same operation in Office online and it worked perfectly. This means that this issue occurs only in Office 365 Word Desktop. I had faced the same issue in Aug 2018. But it looks like the bug still exists.



I am running Word desktop Version 1808 (Build 10730.20304 Click-to-Run)










share|improve this question
























  • I tried to reproduce. If I save the Word document, the custom property is saved. If I close the Word document without saving, the property is not saved. But that's what I'd expect. Word Online has an autosave feature, so that's probably why it works there without explicitly saving.

    – Rick Kirkham
    Mar 21 at 16:35











  • I modified the code to include context.document.save(); But even then the custom properties are not saved. Even Word desktop has an autosave feature. This is not a feature but a bug.

    – Codecrasher99
    Mar 22 at 6:43











  • I can't reproduce. The bug that's referred to in your Aug 2018 question is about an unneeded prompt to save. But that is not your symptoms.

    – Rick Kirkham
    Mar 22 at 7:44











  • You mentioned that this happened in Aug 2018 - have you updated your Office since/

    – Mavi Domates
    Mar 22 at 8:25











  • Yes my office version has been updated since then.

    – Codecrasher99
    Mar 22 at 8:37













0












0








0








My office js Word add-in code saves a custom property to the document customproperty collection. The code for saving is as below.



Word.run(function (context) 
//method accepts property name plus value
context.document.properties.customProperties.add(propertyname, value);
context.document.save();
return context.sync()
.then(function ()
console.log("Property saved");
)
.catch (function (e)
console.log("Error occured inserting property " + e.message);

);
);


After my add-in executes I can see the custom property when I click on Info->Properties->AdvancedProperties->Custom. But when i close the Office 365 Word desktop application and reopen the document I find the custom property has not been saved. So I opened the Word document again in desktop and then again ran my add-in. This time I also typed some characters in the document and then closed the document. Now when I reopened the document I found that the custom properties are saved correctly. This means that custom properties are not getting saved when we execute the word context sync operation.



I then performed the same operation in Office online and it worked perfectly. This means that this issue occurs only in Office 365 Word Desktop. I had faced the same issue in Aug 2018. But it looks like the bug still exists.



I am running Word desktop Version 1808 (Build 10730.20304 Click-to-Run)










share|improve this question
















My office js Word add-in code saves a custom property to the document customproperty collection. The code for saving is as below.



Word.run(function (context) 
//method accepts property name plus value
context.document.properties.customProperties.add(propertyname, value);
context.document.save();
return context.sync()
.then(function ()
console.log("Property saved");
)
.catch (function (e)
console.log("Error occured inserting property " + e.message);

);
);


After my add-in executes I can see the custom property when I click on Info->Properties->AdvancedProperties->Custom. But when i close the Office 365 Word desktop application and reopen the document I find the custom property has not been saved. So I opened the Word document again in desktop and then again ran my add-in. This time I also typed some characters in the document and then closed the document. Now when I reopened the document I found that the custom properties are saved correctly. This means that custom properties are not getting saved when we execute the word context sync operation.



I then performed the same operation in Office online and it worked perfectly. This means that this issue occurs only in Office 365 Word Desktop. I had faced the same issue in Aug 2018. But it looks like the bug still exists.



I am running Word desktop Version 1808 (Build 10730.20304 Click-to-Run)







office-js






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 22 at 10:18







Codecrasher99

















asked Mar 21 at 15:28









Codecrasher99Codecrasher99

6317




6317












  • I tried to reproduce. If I save the Word document, the custom property is saved. If I close the Word document without saving, the property is not saved. But that's what I'd expect. Word Online has an autosave feature, so that's probably why it works there without explicitly saving.

    – Rick Kirkham
    Mar 21 at 16:35











  • I modified the code to include context.document.save(); But even then the custom properties are not saved. Even Word desktop has an autosave feature. This is not a feature but a bug.

    – Codecrasher99
    Mar 22 at 6:43











  • I can't reproduce. The bug that's referred to in your Aug 2018 question is about an unneeded prompt to save. But that is not your symptoms.

    – Rick Kirkham
    Mar 22 at 7:44











  • You mentioned that this happened in Aug 2018 - have you updated your Office since/

    – Mavi Domates
    Mar 22 at 8:25











  • Yes my office version has been updated since then.

    – Codecrasher99
    Mar 22 at 8:37

















  • I tried to reproduce. If I save the Word document, the custom property is saved. If I close the Word document without saving, the property is not saved. But that's what I'd expect. Word Online has an autosave feature, so that's probably why it works there without explicitly saving.

    – Rick Kirkham
    Mar 21 at 16:35











  • I modified the code to include context.document.save(); But even then the custom properties are not saved. Even Word desktop has an autosave feature. This is not a feature but a bug.

    – Codecrasher99
    Mar 22 at 6:43











  • I can't reproduce. The bug that's referred to in your Aug 2018 question is about an unneeded prompt to save. But that is not your symptoms.

    – Rick Kirkham
    Mar 22 at 7:44











  • You mentioned that this happened in Aug 2018 - have you updated your Office since/

    – Mavi Domates
    Mar 22 at 8:25











  • Yes my office version has been updated since then.

    – Codecrasher99
    Mar 22 at 8:37
















I tried to reproduce. If I save the Word document, the custom property is saved. If I close the Word document without saving, the property is not saved. But that's what I'd expect. Word Online has an autosave feature, so that's probably why it works there without explicitly saving.

– Rick Kirkham
Mar 21 at 16:35





I tried to reproduce. If I save the Word document, the custom property is saved. If I close the Word document without saving, the property is not saved. But that's what I'd expect. Word Online has an autosave feature, so that's probably why it works there without explicitly saving.

– Rick Kirkham
Mar 21 at 16:35













I modified the code to include context.document.save(); But even then the custom properties are not saved. Even Word desktop has an autosave feature. This is not a feature but a bug.

– Codecrasher99
Mar 22 at 6:43





I modified the code to include context.document.save(); But even then the custom properties are not saved. Even Word desktop has an autosave feature. This is not a feature but a bug.

– Codecrasher99
Mar 22 at 6:43













I can't reproduce. The bug that's referred to in your Aug 2018 question is about an unneeded prompt to save. But that is not your symptoms.

– Rick Kirkham
Mar 22 at 7:44





I can't reproduce. The bug that's referred to in your Aug 2018 question is about an unneeded prompt to save. But that is not your symptoms.

– Rick Kirkham
Mar 22 at 7:44













You mentioned that this happened in Aug 2018 - have you updated your Office since/

– Mavi Domates
Mar 22 at 8:25





You mentioned that this happened in Aug 2018 - have you updated your Office since/

– Mavi Domates
Mar 22 at 8:25













Yes my office version has been updated since then.

– Codecrasher99
Mar 22 at 8:37





Yes my office version has been updated since then.

– Codecrasher99
Mar 22 at 8:37












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55283945%2fdocument-custom-properties-are-not-saved-in-word-desktop%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55283945%2fdocument-custom-properties-are-not-saved-in-word-desktop%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

용인 삼성생명 블루밍스 목차 통계 역대 감독 선수단 응원단 경기장 같이 보기 외부 링크 둘러보기 메뉴samsungblueminx.comeh선수 명단용인 삼성생명 블루밍스용인 삼성생명 블루밍스ehsamsungblueminx.comeheheheh

155 수학 과학 기타 둘러보기 메뉴eh추가해eh문서를 완성해