@RameshB16753552

What are the keys defined on your class and the params that you're passing?

Keys defined for your class should match with the parameters you are passing while performing lookup.

@RameshB16753552

Obj-Open-By-Handle fails only when the handle you pass isn’t a real pzInsKey for that class, so start by opening any known AccountDetails record and copy its pxInsHandle from the clipboard; compare it to the value you’re building (the format and key order must match exactly). Next, open the CG-ACGCBank-Data-AccountDetails data type and check the Keys section; make sure the parameters you pass (and their order) match those keys, otherwise the handle string you generate won’t hit anything. If you’re saving via a Savable Data Page and then immediately calling Obj-Open-By-Handle in the same request, make that save immediate (WriteNow on the savable data page) or add a Commit otherwise the row may not exist yet when you try to open it. Also confirm you’re not feeding pyID into Obj-Open-By-Handle; that method needs pzInsKey if you only have the visible keys, use Obj-Open instead.Finally, sanity-check that your Save Data Page smart shape is wired to the correct savable data page or autopopulated property with all key params filled, and that the class is mapped to the right table (Data-Admin-DB-Table).  If you align the key definition, the exact handle value, and commit timing, that “Unable to open an instance using the given inputs” error goes away.