> For the complete documentation index, see [llms.txt](https://docs.ohmyapp.io/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ohmyapp.io/main/guide/faq/logic/8.md).

# 8. 입력된 데이터를 숫자(int) 형태로 변환하고 싶어요

Android에서 숫자 편집기 블록으로 데이터를 입력하면 문자열(String) 형태로 저장돼요.

이럴 경우 계산에 활용할 수 없어요.

숫자 형태의 데이터가 필요할 때 자동으로 형 변환 하는 법을 알려드릴게요.

<div align="left"><figure><img src="/files/GB8bNjc1cytkBTMkDBZS" alt="" width="375"><figcaption></figcaption></figure></div>

<figure><img src="/files/gtfxOlepBfogxRdbR6Xo" alt=""><figcaption></figcaption></figure>

<div align="left"><figure><img src="/files/OjqhKm4f5dBrZMPLP8OC" alt="" width="356"><figcaption></figcaption></figure></div>

## If When

등록할 때

## Where

해당 메타 ID

## Condition\_New data query

setValue로 방금 기록된 데이터를 숫자(int) 형태로 형 변환해서 저장

## Then

기존 데이터를 수정

* 수정하고 싶은 문서들의 검색 조건 : 방금 생성된 데이터의 ID
* 수정하려는 내용
  * 해당 메타의 항목 ID에 알맞은 값이 들어가도록 설정

24.09.04 Jihwan


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ohmyapp.io/main/guide/faq/logic/8.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
