@memberjunction/core 0.9.163 → 0.9.164

package/dist/generic/baseEntity.d.ts

@@ -149,8 +149,8 @@ export declare abstract class BaseEntity {
     InnerLoad(PrimaryKeyValues: PrimaryKeyValue[], EntityRelationshipsToLoad?: string[]): Promise<boolean>;
     protected ValidatePrimaryKeyArray(PrimaryKeyValues: PrimaryKeyValue[]): void;
     /**
-     * This method is meant to be used only in situations where you are sure that the data you are loading is current in the database. The Dirty flags and other internal state will assume what is loading from
-     * the object is equivalent to what is in the database. Generally speaking, you should use Load() instead of this method. The main use case(s) where this makes sense are:
+     * This method is meant to be used only in situations where you are sure that the data you are loading is current in the database. MAKE SURE YOU ARE PASSING IN ALL FIELDS.
+     * The Dirty flags and other internal state will assume what is loading from the data parameter you pass in is equivalent to what is in the database. Generally speaking, you should use Load() instead of this method. The main use case(s) where this makes sense are:
      *  (1) On the server if you are pulling data you know is fresh from say the result of another DB operation
      *  (2) If on any tier you run a fresh RunView result, that gives you data from the database, you can then instantiate objects via Metadata.GetEntityObject() and then use this with the result from the RunView call
      *  *** Note: for the #2 use case, when you call the RunView Object RunView() method with the ResultType='entity_object', you'll get an array of BaseEntity-derived objects instead of simple objects, that functionality utilizes this method

package/dist/generic/baseEntity.js

@@ -561,8 +561,8 @@ class BaseEntity {
         }
     }
     /**
-     * This method is meant to be used only in situations where you are sure that the data you are loading is current in the database. The Dirty flags and other internal state will assume what is loading from
-     * the object is equivalent to what is in the database. Generally speaking, you should use Load() instead of this method. The main use case(s) where this makes sense are:
+     * This method is meant to be used only in situations where you are sure that the data you are loading is current in the database. MAKE SURE YOU ARE PASSING IN ALL FIELDS.
+     * The Dirty flags and other internal state will assume what is loading from the data parameter you pass in is equivalent to what is in the database. Generally speaking, you should use Load() instead of this method. The main use case(s) where this makes sense are:
      *  (1) On the server if you are pulling data you know is fresh from say the result of another DB operation
      *  (2) If on any tier you run a fresh RunView result, that gives you data from the database, you can then instantiate objects via Metadata.GetEntityObject() and then use this with the result from the RunView call
      *  *** Note: for the #2 use case, when you call the RunView Object RunView() method with the ResultType='entity_object', you'll get an array of BaseEntity-derived objects instead of simple objects, that functionality utilizes this method

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memberjunction/core",
-  "version": "0.9.163",
+  "version": "0.9.164",
   "description": "MemberJunction: Core Library including Metadata, Application, Entity Retrieval and Manipulation, and Utilities",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",